You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is will be very useful if API-Console will be support discriminator feature.
When convert RAML to AmfGraph via webapi-parser we have data about root type in raml-shapes:inherits node. (But if convert via api-console-cli, info about root type is lost)
When convert OAS2 to AmfGraph we have data about root type in shacl:and node.
Will be cool if data about root type displayed in types list. And root type have links to all child types (as in JavaDoc "Direct Known Subclasses" and class hierarchy)
The text was updated successfully, but these errors were encountered:
@jstoiko i use last version of webapi-parser@0.5.0
and i use last version of api-console-cli@2.0.3
if I'm not mistaken, both libs have depends amf-client-js@4.0.4, but result is different.
I forgot to say, webapi-parser i use in java code, maybe it is important.
It is will be very useful if API-Console will be support discriminator feature.
When convert RAML to AmfGraph via
webapi-parser
we have data about root type inraml-shapes:inherits
node. (But if convert via api-console-cli, info about root type is lost)When convert OAS2 to AmfGraph we have data about root type in
shacl:and
node.Will be cool if data about root type displayed in types list. And root type have links to all child types (as in JavaDoc "Direct Known Subclasses" and class hierarchy)
The text was updated successfully, but these errors were encountered: