-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tree pruning #252
Labels
Comments
First define basic description of layering. Good possible solution for deletion. |
Closed
I am doing some cleanup closing all issues created 2021 or earlier where there have been no activity 2023 or later. If you still consider this issue relevant feel free to reopen it add and add a comment on how you would like to see progress on this one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would like to propose a solution to two issues,
The idea is to introduce a new key-value property (metadata) named "prune", that would have a value in the format of either a single string or an array of strings. This value would consist one or more relative paths, representing absolute paths in combination with the path to the node in which it is found. The "pruning", i. e. removal of nodes would then be applied by the tool for the node addressed by the absolute path, and any subtree below this path.
An example of 1. is shown below where the instantiation will lead to a tree representing Pos1, and Pos3 seats in Row1, Pos1, Pos2, and Pos3 seats in Row2, and a Pos2 seat in Row3.
An example of 2. could be the following that would remove the entire OBD branch, assuming it is part of the YAML tree.
The "prune" property would typically be added in the deployment phase using the layering mechanism, and then it would be the responsibility of the tool to prune its output accordingly.
The text was updated successfully, but these errors were encountered: