-
Notifications
You must be signed in to change notification settings - Fork 94
Uses Augmentation #272
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
base: master
Are you sure you want to change the base?
Uses Augmentation #272
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -624,13 +624,13 @@ type Uses struct { | |
| Parent Node `yang:"Parent,nomerge" json:"-"` | ||
| Extensions []*Statement `yang:"Ext" json:"-"` | ||
|
|
||
| Augment *Augment `yang:"augment" json:",omitempty"` | ||
| Description *Value `yang:"description" json:",omitempty"` | ||
| IfFeature []*Value `yang:"if-feature" json:"-"` | ||
| Refine []*Refine `yang:"refine" json:"-"` | ||
| Reference *Value `yang:"reference" json:"-"` | ||
| Status *Value `yang:"status" json:"-"` | ||
| When *Value `yang:"when" json:",omitempty"` | ||
| Augment []*Augment `yang:"augment" json:",omitempty"` | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we create a different field here, since this means that this change is backwards-incompatible for existing API users. There was some discussion historically about making such changes for YANG 1.1. If we don't do this, then we need to mark this as goyang v2. I'd prefer to see whether we can group up other API changes that would be needed to fully support y1.1 into such a release.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm unsure what exactly you want me to do here.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't support changing I suggest this is implemented using a new field |
||
| Description *Value `yang:"description" json:",omitempty"` | ||
| IfFeature []*Value `yang:"if-feature" json:"-"` | ||
| Refine []*Refine `yang:"refine" json:"-"` | ||
| Reference *Value `yang:"reference" json:"-"` | ||
| Status *Value `yang:"status" json:"-"` | ||
| When *Value `yang:"when" json:",omitempty"` | ||
| } | ||
|
|
||
| func (Uses) Kind() string { return "uses" } | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We haven't added this kind of error checking elsewhere -- I wonder whether we should try and include the parsed YANG version somewhere in the output entry. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we want to be strict then thats probably a good idea.