Undertanding implementation of `TextInput` about bevy_simple_text_input HOT 2 CLOSED

Bevy UI hierarchies require the components of NodeBundle to work properly.

The current design where a user spawns both a NodeBundle and TextInput component together comes from my general aversion to working with nested bundles. That is, this:

commands.spawn((
    NodeBundle { /* ... */ },
    TextInput { /* ... */ }
))

feels a bit nicer to me than

commands.spawn(TextInputBundle {
    node: NodeBundle { /* ... */ },
    text_input: TextInput { /* ... */ }
})

But now that I'm typing this all out, I'm not sure about the decision.

Maybe your instinct is right and we can remove one layer of NodeBundle. I think there may have been some slightly surprising behavior with borders / clipping though that made that extra layer necessary though.

from bevy_simple_text_input.

Ok, I see. Thank you :)

Regarding the decision, I think it is clearer to use TextInputBundle.

from bevy_simple_text_input.