Button component only allows one child

[jquesada2016]

Take the following example:

fn main() {
    element! {
        Button {
            Text(content: "<")
            #( Some(element! { Text(content: "Click me") }) )
            Text(content: ">")
        }
    }
    .print()
}

This code will print <, rather than <Click me>.

In my case, I was trying to wrap the button component to add some default styling, and adding <...> to whatever components were passed in, but I saw in the source code the button component only gets a single next child, rather than attempting to render all children.

A workaround is to put the children in a View, but I thought it was a good idea to raise this issue. :(

[ccbrown]

It would be trivial to allow for this, I just wasn't sure at the time what should happen if the button gets more than one child. How should they be laid out? In a column? In a row? Should there be a gap between children?

I figured it would be best to force the user to make that decision.

In HTML, if you give a <button> multiple flex children, they'll be laid out in a column, which made me second guess whether laying everything out in a row was the right answer.

[jquesada2016]

Well, I wouldn't mind forcing consumers to use a single child, but it would ideally give a warning or a panic, or allow children to be a single element, and provide a compilation error so one knows that this is intentional behavior :)

If there were a way to spread props, then perhaps the button could extend those from View, just adding the has_focus and on_click handlers, and then the user could decide what to do.