Make system stepping a runtime setting instead of a compile-time feature

未关闭
#26,326 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
backend, devtools

调研方向

Start by reading the stepping feature and handlers in bevy_ecs and bevy_remote, then trace how bevy_inspector invokes them. The issue suggests moving stepping to a runtime setting and possibly grouping dev-only ECS features, but leaves the design open. Done means remote clients can use stepping without enabling it for the whole app, with the runtime and release-build behavior agreed and covered.

由索引模型根据 Issue 内容生成。

描述

A-Dev-Tools A-ECS D-Modest S-Needs-Design X-Contentious

System stepping is controlled by the bevy_debug_stepping feature, which turns stepping on for the whole app. Because bevy_remote gates its stepping methods behind the same feature, a remote client like the inspector could only use them by enabling stepping in its own app (#26200 now keeps only the handlers gated).

Stepping should probably be a runtime setting, maybe as part of a set of dev-only ECS features that can be turned off in release builds to reduce attack surface and binary size. This touches bevy_ecs, bevy_remote and bevy_inspector.

Raised by alice-i-cecile on #26200.

主要语言
Rust
星标
49.7k
派生
5k
平均合并
3 天 19 小时
30 天内合并 PR
134

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

bevyengine/bevy 的其他 Issue

查看 bevyengine/bevy 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。