Description
Is your feature request related to a problem? Please describe.
When I first used the schema editor, I've tried validating my schema on swagger.io. It was only after a bit of trial and error that I found out, that I had to enter JSON-Schema parameters. I think that this behavior is counter-intuitive since the goal of the website is that we do not have to deal with the schema that is defined under the hood, but instead are able to do everything from a GUI.
Describe the solution you'd like
I'd suggest implementing a GUI for creating Schemas - the users enter a parameter, e.g. foo
, they select the type, e.g. string
, and then get all the options that JSON-Schema offers for strings. The actual schema is created under the hood, and developers can switch to the JSON-Schema view, when they want/need to.