Converted additional leafrefs into leafref tuples #306
Conversation
This file contains 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
Collaborator
karthik-sethuraman
commented
Mar 25, 2018
karthik-sethuraman
commented
- fixed the remaining object-references that were previously described using single leafref to now use a grouping that contains tuple of leafref statements - one for each ancestor node of the referenced node
- updated the .tree files
|
👍 ONOS yang-tools was able to parse this. |
|
looks good to me |
karthik-sethuraman
merged commit bea1fb8
into
Open-Network-Models-and-Interfaces-ONMI:develop
onlab-gerrit
pushed a commit
to opennetworkinglab/onos
that referenced
this pull request
Mar 26, 2018
- based on Open-Network-Models-and-Interfaces-ONMI/TAPI#306 Change-Id: Ib668ff5dfdac78d06557c4d932f1fe614cdde344
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.