Skip to content
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.

Sign up for GitHub

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

Jump to bottom

YANG: key statement in rpc/notification list #148

Closed
hjelmeland opened this issue Nov 6, 2020 · 1 comment
Closed

YANG: key statement in rpc/notification list #148

hjelmeland opened this issue Nov 6, 2020 · 1 comment
Labels
bug

Comments

@hjelmeland
Copy link

Clixon require key statement in lists inside rpc and notification. AFAIKT RFC only require key statement for configuration data.
@olofhagsand olofhagsand added the bug label Nov 6, 2020
olofhagsand added a commit that referenced this issue Dec 1, 2020
@olofhagsand
* Error-type changed from protocol to application for data-not-unique…
e46f6f4 
… netconf/restconf errors

* Added new revision of main example yang: `clixon-example@2020-12-01.yang`
* Fixed [YANG: key statement in rpc/notification list #148](#148)
  * Do not check uniqueness among lists without keys
@olofhagsand
Copy link
Member

@hjelmeland the fix ^ addresses the sub-error:

  • Do not check uniqueness (of XML) among lists without keys
    As far as I can see, key-less lists were/are allowed in YANG for state/notification/rpc.
    The error I could find was that XML of such lists were checked for non-uniqueness, as if they had keys.
    Please come back with an example testcase that fails if this fix does not work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hjelmeland @olofhagsand