[YANGTOOLS-224] Yangtools fails to parse module with yin-element statement before vendor extension Created: 24/Jul/14 Updated: 10/Apr/22 Due: 29/Jul/14 Resolved: 29/Jul/14 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Giles Heron | Assignee: | Martin Vitez |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Mac OS |
||
| External issue ID: | 1413 |
| Description |
|
Yangtools is failing to parse modules where there's a "yin-element true" statement between an "argument" statement and a vendor extension relating to that augment. So: extension foo { } } is ok. But: extension foo { argument text { yin-element true; vendor:bar { type string; } } is not. If I move the yin-element statement below the vendor extension it parses ok. The logs I get look like: "extraneous input 'description' expecting {'}', 'uses', 'typedef', 'rpc', 'notification', 'list', 'leaf-list', 'leaf', 'identity', 'grouping', 'feature', 'deviation', 'extension', 'container', 'choice', 'augment', 'anyxml', IDENTIFIER} in module..." The vendor extension has a "description" in it. If I delete that this parses ok. |
| Comments |
| Comment by Martin Vitez [ 28/Jul/14 ] |
|
Proposed patch: |