[NETCONF-1056] OpenApi: Do not use ArrayNode to store parameters Created: 14/Jun/23 Updated: 14/Jul/23 Resolved: 14/Jul/23 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | restconf-openapi |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0 |
| Type: | Task | Priority: | Medium |
| Reporter: | Ivan Hrasko | Assignee: | Yaroslav Lastivka |
| Resolution: | Done | Votes: | 0 |
| Labels: | pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
We are using ArrayNode to store parameters. We use it only as a List which stores parameter names. Do not use ArrayNode as addPath (et. al) method parameter for parameters and use List instead. In addition, create dedicated Java class to store parameters as described in https://swagger.io/specification/#parameter-object and use it in Operation.java. Along the way we will also eliminate OperationBuilder#getTypeParentNode method. |
| Comments |
| Comment by Ivan Hrasko [ 20/Jun/23 ] |
|
Maybe Map or Set would be more better to help us create better solution for |
| Comment by Ivan Hrasko [ 20/Jun/23 ] |
|
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. |