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-1056 netconf <p>We are using <b>ArrayNode</b> to store parameters. We use it only as a <b>List</b> which stores parameter names. Do not use <b>ArrayNode</b> as <b>addPath (et. al)</b> method parameter for parameters and use List instead. In addition, create dedicated Java class to store parameters as described in <a href="https://swagger.io/specification/#parameter-object" class="external-link" target="_blank" rel="nofollow noopener">https://swagger.io/specification/#parameter-object</a> and use it in <b>Operation</b>.java. Along the way we will also eliminate <b>OperationBuilder</b>#<b>getTypeParentNode</b> method.</p> NETCONF-1056

OpenApi: Do not use ArrayNode to store parameters

Task Medium Resolved Done Yaroslav Lastivka Ivan Hrasko pt Wed, 14 Jun 2023 08:09:07 +0000 Fri, 14 Jul 2023 11:26:21 +0000 Fri, 14 Jul 2023 11:26:17 +0000 7.0.0 restconf-openapi 0 1 <p>Maybe Map or Set would be more better to help us create better solution for <a href="https://jira.opendaylight.org/browse/NETCONF-1060" title="OpenApi: Broken parameters logic" class="issue-link" data-issue-key="NETCONF-1060"><del>NETCONF-1060</del></a>.</p> <p>Yes, we will need to deal with "discriminator" logic. When at place for parameters: param, param2, param, param2 the expected output is: param, param2, param1, param21.</p> Relates NETCONF-938 Development Rank 0|i045gv: