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
First of all this is really awesome thanks! I was wondering if maybe the required properties should be highlighted some how, or maybe even pre-filled (just the keys) so you can go through and define the values.
It's super handy as-is but it's hard to tell which are required.
Maybe it makes more sense to validate the entire JSON file as you're writing it and show errors or something.
The text was updated successfully, but these errors were encountered:
I guess it would make sense. I don't want to mix validation into this package, but I'm absolutely ok with making the required fields more obvious. This is the complete list of customizations that autocomplete-plus allows: https://github.com/atom/autocomplete-plus/wiki/Provider-API#suggestions
From this what I currently use is:
displayText - what you see as key name or value (like statistics on the screenshot) snippet - this is what is being added to the document when the suggestion is selected description - schema description if available rightLabel - the type like enum or number type - marks the type of the suggestion (p on the left). should be replaced by an icon but for some reason it isn't.
What do you think should be added? Maybe just order the required ones first? Or add leftLabel with the text required or optional?
Hmm the required ones first and maybe having some icon or label like you mentioned would be killer. Might be nice to display the examples in that description part as well. Your call of course :D it's already awesome but that'd help!
Ok will take a look at it. Can't promise anything before the weekend though. Also about the examples, that is a json schema v6 feature right? It might be interesting to explore the new draft for json schema, since currently it only supports stuff that's available in v4.
First of all this is really awesome thanks! I was wondering if maybe the required properties should be highlighted some how, or maybe even pre-filled (just the keys) so you can go through and define the values.
It's super handy as-is but it's hard to tell which are required.
Maybe it makes more sense to validate the entire JSON file as you're writing it and show errors or something.
The text was updated successfully, but these errors were encountered: