https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-215 netconf <p>For a YANG RPC like netconf POST to /operations/toaster:make-toast, that Data Type Model Schema for input is { } even though it should be something like {"input" : </p> { "toaster:toasterDoneness" : "10", "toaster:toasterToastType":"wheat-bread" } <p> } it seems some mapping into Swagger's JSON isn't generated quite right there.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-215

API Explorer Model Schema Data Type 'Click to set as parameter value' is empty for YANG RPC POST to /operations/

Bug Resolved Done Miroslav Kovac Michael Vorburger Thu, 2 Jun 2016 16:41:23 +0000 Fri, 15 Mar 2019 22:22:25 +0000 Thu, 22 Sep 2016 12:00:28 +0000 restconf-nb 0 2 <p><a href="https://git.opendaylight.org/gerrit/#/c/45580/2" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/45580/2</a></p> <p>I've just attempted to manually test c/45580/2, and seen that instead of the original:</p> <p>{ } </p> <p>it's now a bit better, but still not really working out-of-the-box:</p> <p>{<br/> "toasterDoneness": "integer",<br/> "toasterToastType": {}<br/> }</p> <p>This is still wrong, as from what little I understand it should rather be something like:</p> <p>{<br/> "input" : </p> { "toasterDoneness" : "1", "toasterToastType": "wheat-bread" } <p>}</p> <p>Note the main diff is the missing "input" kind of wrap around it. (Putting valid example values, like "1" instead of "integer" and "wheat-bread" instead of {} would be cool too I guess, but I can open a separate issue about that, if you prefer.)</p> <p>PS: The c/45580 also doesn't include any non-regression test (but that's not really my call).</p> <p>(In reply to Michael Vorburger from comment #2)<br/> &gt; I've just attempted to manually test c/45580/2, and seen that instead of the<br/> &gt; original:<br/> &gt; <br/> &gt; { } <br/> &gt; <br/> &gt; it's now a bit better, but still not really working out-of-the-box:<br/> &gt; <br/> &gt; {<br/> &gt; "toasterDoneness": "integer",<br/> &gt; "toasterToastType": {}<br/> &gt; }<br/> &gt; <br/> &gt; This is still wrong, as from what little I understand it should rather be<br/> &gt; something like:<br/> &gt; <br/> &gt; {<br/> &gt; "input" : </p> { &gt; "toasterDoneness" : "1", &gt; "toasterToastType": "wheat-bread" &gt; } <p>&gt; }<br/> &gt; <br/> &gt; Note the main diff is the missing "input" kind of wrap around it. (Putting<br/> &gt; valid example values, like "1" instead of "integer" and "wheat-bread"<br/> &gt; instead of {} would be cool too I guess, but I can open a separate issue<br/> &gt; about that, if you prefer.)<br/> &gt; <br/> &gt; PS: The c/45580 also doesn't include any non-regression test (but that's not<br/> &gt; really my call).</p> <p>Thank you for reply<br/> Yes I know about that but this is opened as bug -&gt; <a href="https://bugs.opendaylight.org/show_bug.cgi?id=5997" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=5997</a><br/> I fixed it so it would do the same thing as with config requests. Whenever the other bug will be fixed it should resolve this too. And I am currently working on that. If you want me to fix it in this bug i can do that too. But since there is opened bug for that I thought it would be better to do it there because the resolution will most likely be the same. </p> <p>As for putting valid example values, separate issue would be better, cause it doesn`t have much to do with this and it should also be in config requests. And that would be an improvement I guess and not a bug.</p> <p>&gt; for putting valid example values, separate issue would be better</p> <p>=&gt; <a href="https://jira.opendaylight.org/browse/NETCONF-278" title="API Explorer Model Schema Data Type &#39;Click to set as parameter value&#39; valid example values" class="issue-link" data-issue-key="NETCONF-278"><del>NETCONF-278</del></a></p> Blocks NETCONF-214 Development External issue ID 5998 External issue URL Issue Type ODL SR Target Milestone Rank 0|i01x5z: