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 type range statement does not support multiple values #59

Closed
olofhagsand opened this issue Dec 1, 2018 · 1 comment
Closed

yang type range statement does not support multiple values #59

olofhagsand opened this issue Dec 1, 2018 · 1 comment
Labels
bug

Comments

@olofhagsand
Copy link
Member

The Yang range statement does not support multiple values (RFC7895 sec 9.2.4).
For example

type uint8 {
      range "1..14 | 36  | 48";
}

is not supported
olofhagsand added a commit that referenced this issue Feb 5, 2019
@olofhagsand
* Partially corrected: [yang type range statement does not support mu…
19343c2 
…ltiple values](#59).

  * Should work for netconf and restconf, but not for CLI.
* Fixed again: [Range parsing is not RFC 7950 compliant](#71)
@olofhagsand
Copy link
Member Author

Works for netconf and restconf.
Does not work for CLI generated code.

@olofhagsand olofhagsand mentioned this issue Feb 28, 2019
Closed
olofhagsand added a commit to clicon/cligen that referenced this issue Mar 4, 2019
@olofhagsand
* Added support for multiple range and length statements for number a…
706dd20 
…nd string types. This means thatthe following is allowed, for example:

  * See [yang type range statement does not support multiple values](clicon/clixon#59)
olofhagsand added a commit that referenced this issue Mar 4, 2019
@olofhagsand
[yang type range statement does not support multiple values](#59)
b182e86 
[Multiple ranges support](#78)
Restructured "cb" parameter in cli_generate.c
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
1 participant
@olofhagsand