-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
bevy_feathers testbed example #24489
Copy link
Copy link
Open
Labels
A-UIGraphical user interfaces, styles, layouts, and widgetsGraphical user interfaces, styles, layouts, and widgetsC-FeatureA new feature, making something new possibleA new feature, making something new possibleC-TestingA change that impacts how we test Bevy or how users test their appsA change that impacts how we test Bevy or how users test their appsS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!This issue is ready for an implementation PR. Go for it!
Description
Metadata
Metadata
Assignees
Labels
A-UIGraphical user interfaces, styles, layouts, and widgetsGraphical user interfaces, styles, layouts, and widgetsC-FeatureA new feature, making something new possibleA new feature, making something new possibleC-TestingA change that impacts how we test Bevy or how users test their appsA change that impacts how we test Bevy or how users test their appsS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!This issue is ready for an implementation PR. Go for it!
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
Needs SME Triage
What problem does this solve or what need does it fill?
The
bevy_featherscrate is quite complex, making it easy to introduce subtle bugs. It can be challenging to write conventional tests for visual theming issues.What solution would you like?
A dedicated feathers testbed example using a variety of themes and features to help verify that styling is applied correctly.
This could be included in
testbed_ui, but IMO it's better to keeptestbed_uifocused on lower-level technical concerns such as layout and rendering, and have a separate testbed for Feathers-specific theming and styling.