Add entity and resource inspection to bevy_dev_tools - #25845
Merged
alice-i-cecile merged 1 commit intoSep 20, 2026
Merged
Conversation
jbuehler23
force-pushed
the
jackdaw/inspector-entity-types
branch
from
September 19, 2026 06:20
aed6a86 to
161a40d
Compare
jbuehler23
added
C-Feature
Zeophlite
approved these changes
Sep 19, 2026
alice-i-cecile
approved these changes
Sep 20, 2026
alice-i-cecile
added
S-Ready-For-Final-Review
Member
|
Thanks for the small improvements :D |
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Sep 20, 2026
jbuehler23
force-pushed
the
jackdaw/inspector-entity-types
branch
from
September 20, 2026 21:41
161a40d to
42e73a1
Compare
gregcsokas
pushed a commit
to gregcsokas/bevy
that referenced
this pull request
Sep 21, 2026
# Objective Part of bevyengine#23013. Add entity and resource inspection to the inspection module, on top of the component inspection that landed in bevyengine#25823. This is what the inspector UI and the remote front end will consume. Ported from feathers_inspector, phase 4.2 of the upstreaming strategy there. Related to bevyengine#25007 and bevyengine#25818. # Solution - an entity inspection carrying the resolved label, spawn details, the component inspections and the total memory size, with a display impl - a resource inspection carrying the name, value string, type id, memory size and type registration - settings and error types for each - extension trait methods on the world for inspect, inspect with a cached metadata map, inspect resource by type or id, and inspect all resources - command helpers that log the result A few small differences from feathers_inspector. Resource entities get labelled with the resource's short name. Memory size is just the sum of the component sizes. Missing entities return an error instead of panicking, and spawn details are only filled in when they're available. # AI disclosure AI assistance was used to help port these changes and to plan this upstream series from our existing Jackdaw functionality. All changes were reviewed by a human before submission.
mockersf
pushed a commit
to mockersf/bevy
that referenced
this pull request
Sep 24, 2026
# Objective Part of bevyengine#23013. The inspection types can be built and displayed but not sent anywhere. Remote tooling needs them as JSON, and an editing client needs the actual field values, not just a display string. Ported from feathers_inspector, phase 4.3 of the upstreaming strategy there. Builds on bevyengine#25823 and bevyengine#25845. # Solution Serde support for the inspection types behind the `serialize` feature, plus structured values. - `with` helpers for component id, archetype id, debug name, storage type, the metadata map and spawn details - serde derives on the inspection and metadata types, with reflected values and type registrations skipped - a `serialized_value` on component and resource inspections, filled through the typed reflect serializer when the new `include_serialized_value` setting is on - the feature now pulls in `serde_json` and the ecs, platform and utils serialize features The two error types with a static string variant are serialize only. Spawn details serialize as tick and location and deserialize to none. # AI disclosure AI assistance was used to help port these changes and to plan this upstream series from our existing Jackdaw functionality. All changes were reviewed by a human before submission.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Objective
Part of #23013.
Add entity and resource inspection to the inspection module, on top of the component inspection that landed in #25823. This is what the inspector UI and the remote front end will consume.
Ported from feathers_inspector, phase 4.2 of the upstreaming strategy there. Related to #25007 and #25818.
Solution
A few small differences from feathers_inspector. Resource entities get labelled with the resource's short name. Memory size is just the sum of the component sizes. Missing entities return an error instead of panicking, and spawn details are only filled in when they're available.
AI disclosure
AI assistance was used to help port these changes and to plan this upstream series from our existing Jackdaw functionality. All changes were reviewed by a human before submission.