Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Json schema for config files #45

Closed
wants to merge 2 commits into from

Conversation

JeroMiya
Copy link

@JeroMiya JeroMiya commented Dec 9, 2014

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.

@JeroMiya
Copy link
Author

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.

@yaniswang
Copy link
Contributor

This file used for IDE?
Can you tell me, the name of ide support the Json schema.

@felixfbecker
Copy link

felixfbecker commented Apr 30, 2016

@yaniswang Visual Studio Code, Visual Studio, WebStorm, Atom, ...
there is also an incomplete list here: http://json-schema.org/implementations.html
@JeroMiya

@yaniswang
Copy link
Contributor

Support ide is too little!

@ArmorDarks
Copy link

Well, now when Visual Studio, Atom and WebStorm took more than half of market, I can't say that support is too little.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Functionality that enhances existing features triage An HTMLHint team member will look at this issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants