feat: add integration API for third-party plugin support#40
Merged
Conversation
Add TOML plugin metadata and demo app showing how third-party plugin authors use the integration API to register properties and bridge editor values to components.
jbuehler23
changed the title
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
1 participant
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.
Summary
Adds a new
bevy_map_integrationcrate that provides a TOML-driven plugin metadata system, allowing third-party crate authors to register properties, inspector sections, and UI contributions with the map editor.New crate:
bevy_map_integrationPluginMeta— serde-compatible struct for declaring plugin name, version, applicable entity types, and properties (string, int, float, bool, filepath, enum, point, color)IntegrationRegistry— runtime registry that indexes plugins and supports querying properties by entity type, inspector sections, and file extensionsPluginManager— filesystem discovery of.tomlplugin files from standard platform directoriesEditorExtension— runtime UI contributions (panels, menu items, inspector sections, toolbar buttons, context menus)editorfeature for Bevy-dependent types (Resourcederive,EditorExtension)Editor integration (
bevy_map_editor)Example:
bevy_aseprite_ultraintegrationexamples/integration/aseprite_ultra.toml— declares 7 properties mapping to bevy_aseprite_ultra's API (aseprite_file, animation_tag, animation_speed, animation_direction, animation_repeat, repeat_count, slice_name) plus editor contributionsexamples/integration/demo.rs— standalone Bevy app that loads the TOML, registers it, queries properties, and demonstrates the component-bridging pattern via logging