bevyengine / bevyengine/bevy

bevy_reflect should be an optional feature in bevy_ui

Open
#20,038 1 comment 2 reactions 0 assignees View on GitHub
A-Reflection A-UI C-Performance C-Usability D-Straightforward S-Ready-For-Implementation X-Uncontroversial
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 16h
Merged PRs (30d)
171

Description

_Originally discussed by @viridia in https://github.com/bevyengine/bevy/pull/20032#discussion_r2193048816_

The same thing should be done for bevy_feathers and bevy_core_widgets, probably in a single PR.

This is useful because reflection adds serious compile time and binary size, and isn't useful for all projects, especially for shipped apps.

Contributor guide

Open the contributing guide

Research direction

Start with the discussion in PR #20032, then inspect the feature and dependency configuration for bevy_ui, bevy_feathers, and bevy_core_widgets. Confirm how reflection is currently enabled and identify the relevant crate checks or tests. Done means reflection can be disabled for these crates without breaking their existing functionality.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
build-system, game-dev
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.