Use defaultValues from NodeTypes.yaml for hierarchy nodes #2
Conversation
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
…ogic This changes the way new hierarchy nodes are auto-created so that all configured default properties (from NodeTypes.yaml) are being applied.
remuslazar
force-pushed
the
bugfix-default-properties
branch
from
2a645e1 to
439a7e5
Compare
Member
|
@remuslazar machst du noch ein PR für upstream (branch 2.2)? |
Member
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Respect the configured default properties in the hierarchy creation logic
This changes the way new hierarchy nodes are auto-created so that
all configured default properties (from NodeTypes.yaml) are being applied.