Closed Vibaswan closed 4 months ago
@Vibaswan : Please change the examples to point to a single field such ipv4.src instead of ipv4.
Another query : How will the description be generated ... will it use the description if supplied by the model author ?
@Vibaswan : Please change the examples to point to a single field such ipv4.src instead of ipv4.
Another query : How will the description be generated ... will it use the description if supplied by the model author ?
@apratimmukherjee corrected the examples Yes the description in auto hierarchy will be provided by the user , it should be mention in the object auto is referring to , updated the example as well
models link where auto hierarchy is been used https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/open-traffic-generator/models/traffic_over_dhcp_interface/artifacts/openapi.yaml&nocors#tag/Configuration/operation/set_config
ipv4_yaml changes https://github.com/open-traffic-generator/models/pull/372/files#diff-b4e391ad7a6920f2c2eb0175634e1655ee8d42bdd7db74e833b99448f8de2116R115
Old Definition
The old way of
auto
works the same way. i.e. by defining auto in features example:New Definition The new definition allows auto to be hierarchical. only valid property inside auto allowed till now is
ref
, which points to a object in the yaml anddefault
which accepts a Boolean value to specify whether auto should be default choice or not.Go snippet to set hierarchical auto
Python snippet to set hierarchical auto
Note:
python SDK exposes choice as of now unlike go SDK and also choices with no properties does not have a getter yet