Migration guide missing: bevy_ui feature no longer includes rendering in 0.17
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- rust
- Domain
- documentation
Research direction
Start with the 0.16 to 0.17 migration guide linked in the issue and review its feature-migration sections. Add the note that bevy_ui no longer implies bevy_ui_render for users with default-features = false, including the required feature example; the guide is done when this silent UI-rendering break is documented.
Written by the indexing model from the issue text.
Description
Originally by @bigmark222 in https://github.com/bevyengine/bevy/issues/22524
Summary
The 0.16 to 0.17 migration guide does not mention that the bevy_ui feature no longer implies rendering functionality. Users who set default-features = false and explicitly list features will have UI that spawns without errors but renders nothing.
The Problem
When migrating to Bevy 0.17 with custom features like:
bevy = { version = "0.17", default-features = false, features = ["bevy_ui", "bevy_text", ...] }
UI entities spawn correctly (logs confirm setup runs), but nothing appears on screen. There are no errors or warnings - the UI is simply invisible.
The Solution
Add bevy_ui_render to the feature list:
bevy = { version = "0.17", default-features = false, features = ["bevy_ui", "bevy_ui_render", "bevy_text", ...] }
Request
Please add this to the 0.16 to 0.17 migration guide under a section like "UI Rendering Feature Separation":
If you use
default-features = falsewith explicit feature flags, note thatbevy_uino longer implies rendering. You must also enablebevy_ui_renderfor UI elements to be visible.
Related
This was previously reported in #21093 but the migration guide was never updated. That issue is the only place this information exists, making it very difficult to discover.
Impact
This is a silent breaking change - code compiles, runs without errors, but produces incorrect output. These are the hardest bugs to diagnose. We spent several hours debugging this before finding #21093 via web search.
- Dominant language
- JavaScript
- Stars
- 249
- Forks
- 451
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bevyengine/bevy-website
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bevyengine/bevy-website#2595 ·
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bevyengine/bevy-website#2593 ·
-
A-News C-Correction D-Trivial S-Ready-For-Implementation X-Uncontroversial
Difficulty 1/5 Under an hour Newbie friendliness 85/100
bevyengine/bevy-website#2574 ·
-
A-Contributing-Guide C-Content D-Straightforward S-Ready-For-Implementation X-Uncontroversial
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bevyengine/bevy-website#2567 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 70/100
bevyengine/bevy-website#2563 · 4 comments · 5 reactions ·
All issues in bevyengine/bevy-website
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·