Details
-
Bug
-
Status: Resolved
-
Resolution: Done
-
None
-
None
-
None
-
Operating System: All
Platform: All
-
5997
Description
If you try to use it (apidoc, Swagger) to e.g. PUT /config/toaster:toaster/ then a dumb end-user like me will naturally find and use that nice "example" parameter support that UI has - on e.g. the (config)toaster parameter, one can click on Model Schema under Data Type where it says e.g.
{ "darknessFactor": "integer" }& 'Click to set as parameter value'.
Doing that will fill in
{ "darknessFactor": "integer" }, make that
{ "darknessFactor": "500" }and click that "Try it out!" button and: "Error parsing input: Schema node with name darknessFactor wasn't found..." - because it would actually have to be: {"toaster": {"darknessFactor": 500}}, only then it works.
Attachments
Issue Links
- blocks
-
NETCONF-215 API Explorer Model Schema Data Type 'Click to set as parameter value' is empty for YANG RPC POST to /operations/
- Resolved