bevy_hints
| Crates.io | bevy_hints |
| lib.rs | bevy_hints |
| version | |
| source | src |
| created_at | 2024-11-25 07:22:10.189058 |
| updated_at | 2024-11-25 07:22:10.189058 |
| description | Hints for future bevy editors to improve usability |
| homepage | https://docs.rs/bevy_hints |
| repository | |
| max_upload_size | |
| id | 1459991 |
| Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
Caleb Yates (ActuallyHappening)
documentation
https://docs.rs/bevy_hints
README
bevy_hints
Hints to future editors that this entity / struct field should be interacted in some way.
Sometimes I want to customize how bevy_editor_pls generates UIs for my reflected values or entities.
But I want my changes to also reflect in future editors without resorting to one-off patches for certain behaviours for just bevy_editor_pls and bevy-inspector-egui,
and I think this is a slightly cleaner way of achieving that goal.