Json schema for config files #45
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks like the original Travis build failure was due to npm flakiness. This change just adds a non-code file, so shouldn't have affected any behavior and I was able to run the tests successfully locally. May have just been a transient npm error. |
|
This file used for IDE? |
|
@yaniswang Visual Studio Code, Visual Studio, WebStorm, Atom, ...
|
|
Support ide is too little! |
|
Well, now when Visual Studio, Atom and WebStorm took more than half of market, I can't say that support is too little. |
thedaviddias
added
enhancement
thedaviddias
force-pushed
the
develop
branch
from
5cf8348 to
25843ac
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are editors and command line validation tools that support json schema for nice auto-complete and validation of json files. It's often useful to provide a json schema when your utility takes a json file as input, as HTMLHint does with the .htmlhintrc json configuration files. I made a schema file for the .htmlhintrc file which includes HTMLHint specific options. It sets "additionalProperties" to true to allow jshint and csshint options, but doesn't include schema for them.