Allow embedding node registration options inline with the behavior tree xml#20
Draft
robin-mueller wants to merge 1 commit into
Draft
Allow embedding node registration options inline with the behavior tree xml#20robin-mueller wants to merge 1 commit into
robin-mueller wants to merge 1 commit into
Conversation
robin-mueller
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.
This pull request adds support for encoding and parsing node registration options as inline XML attributes within behavior tree node elements. This allows node registration options to be specified directly in the XML, using a consistent prefix, and leverages YAML for serialization and parsing.
The main goal of this PR is to make it easier and more straightforward to deploy behaviors with AutoAPMS Studio, where the association between nodes and their node manifests can be made implicitly thanks to the drag and drop feature.
Technically, if all nodes in a tree xml file specify inline registration options, the user does not have to pass a node manifest manually as the necessary information about the registration strategy can be inferred from the build request.