Skip to content
This repository has been archived by the owner on Jun 17, 2023. It is now read-only.

json validation #50

Open
justinabrahms opened this issue Feb 13, 2014 · 7 comments
Open

json validation #50

justinabrahms opened this issue Feb 13, 2014 · 7 comments

Comments

@justinabrahms
Copy link
Owner

It would be nice to have a simple linter that would validate .json files are actually valid json.

@meandavejustice
Copy link

What do you think about also detecting package.json and running against pjv for better suggestions on npm files? This would of course be in addition to a standard json validation. This could always be built as a separate plugin entirely.

@meandavejustice
Copy link

Also I just about have the standard validation done, just having trouble with python regex... as mention in previous tweet...

@scottjab
Copy link
Collaborator

Regarding the pjv stuff that is doable, but I need a fuzzy json linter for chef json. chef is dumb and allows for comments in json.

@meandavejustice
Copy link

@scottjab Nice, I'll keep that in mind. You think we should provide and option? or detect chef files?

@justinabrahms
Copy link
Owner Author

Make a working "this is real json" validator. We can subclass it or make separate ones to validate less-than-real json.

@meandavejustice
Copy link

works 4 me

@scottjab
Copy link
Collaborator

+1 on that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants