[NETCONF-278] API Explorer Model Schema Data Type 'Click to set as parameter value' valid example values Created: 16/Sep/16  Updated: 15/Mar/19  Resolved: 08/Nov/16

Status: Resolved
Project: netconf
Component/s: restconf-nb
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Michael Vorburger Assignee: Miroslav Kovac
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Blocks
is blocked by NETCONF-272 Api explorer does not handle nodes wi... Resolved
is blocked by YANGTOOLS-662 Anyxml is not parsed correctly Resolved

 Description   

As discussed in NETCONF-215 if it's technically possibly (with Swagger) it would be "nice" if the Model Schema under Data Type 'Click to set as parameter value' would put in VALID example values; e.g. "toasterDoneness": "1" instead of "integer", etc.

This would have to take into account various things such as data types, required/mandatory etc. I would imagine that the logic for chosing and example value could be kept trivial - something like if it's numeric, then 0 or 1 or the first possible value (if if's a range), if it's an enum then just the first value, if it's a non-empty list then (recursively) a value for 1 list element, etc.

This is an Enhancement, not a bug. I don't know how feasible this is. NETCONF-215 and NETCONF-214 are clearly higher prioritities, and this one is a nice to have (which would be cool) as a future follow-up after those are settled.



 Comments   
Comment by Miroslav Kovac [ 11/Oct/16 ]

https://git.opendaylight.org/gerrit/#/c/46772/

Generated at Wed Feb 07 20:14:37 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.