bevyengine / bevyengine/bevy

FeathersTextInput needs manually placing in a FeathersTextInputContainer unlike other controls

Open
#24,882 0 comments 0 reactions 0 assignees View on GitHub
A-UI C-Usability D-Straightforward M-Migration-Guide S-Needs-Design
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 22h
Merged PRs (30d)
161

Description

## What problem does this solve or what need does it fill?

Currently to setup a feathers text input you need to do:

```
@FeathersTextInputContainer Children [
MarkerTestValueString
@FeathersTextInput {

}
...
]
```

Which is different to other controls which contain all their decoration.

## What solution would you like?

The current way has been done deliberately in case you want to embed other controls inside the container but outside the text input. This same thing could be achieved with an extra properties or similar...

```
@FeathersTextInput {
@extra_controls: bsn! { ... }
}
...
```

## Alternative

An alternative could be that you have a "bare" property on FeathersTextInput that displays it bare so you can place it as currently, but by default it contains its container. I like that just as much.

Contributor guide

Open the contributing guide

Research direction

The issue names FeathersTextInput and FeathersTextInputContainer but no files or tests. Start by locating those controls and comparing how other controls include their decoration. Clarify whether default containment or a bare/extra-controls option is intended, then add coverage showing the chosen behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
game-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.