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
I was wondering if it would be appropriate to add an option that allows displaying the used references and their names in a separate part of the schema, à la OpenAPI that displays also the defined types, and their constructs.
Maybe the option can be made generic to process all defined keys at the root of the document instead of only the "properties" ?
What do you all think?
Alain
The text was updated successfully, but these errors were encountered:
I think it's a great idea that would make reading the schema more logical. An example in our use case are properties that can be defined under several environment names (dev, qa, etc.) In that case, all definitions link to the first environment in alphabetical order, which is kind of misleading (it's like it would be saying that qa behaves like dev).
I'm not making any promises for an implementation soon, I unfortunately do not work on that library as much as I'd like.
I would of course take the time to review a PR though.
Hi,
Thanks for the great tool!
I was wondering if it would be appropriate to add an option that allows displaying the used references and their names in a separate part of the schema, à la OpenAPI that displays also the defined types, and their constructs.
Maybe the option can be made generic to process all defined keys at the root of the document instead of only the "properties" ?
What do you all think?
Alain
The text was updated successfully, but these errors were encountered: