I'd like some lint tools

[linkslice]

What type of request is this?

New tool idea

Clear and concise description of the feature you are proposing

I used jsonlint.com pretty regularly, but I'd rather not send my json outside to find formatting issues.

Is their example of this tool in the wild?

No response

Additional context

No response

Validations

• Check the feature is not already implemented in the project.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
• Check that the feature can be implemented in a client side only app (IT-Tools is client side only, no server).

[Gorian]

I agree, I have the same concerns. Linting tools I'd like to see:

• JSON
• YAML
• TOML
• XML

[sharevb]

Hi @Gorian , @linkslice ,

• json linter in feat(new tool): JSON Linter #1015
• yaml linter in feat(Yaml Viewer): add parsing validation #957
• XML linter and toml have some converters to json, kind of validators

[Gorian]

Thanks for the links! Just to note, validation - "this is correct enough to convert" - isn't the same as linting - "here's what's wrong, and how to fix it".

As an example, with the TOML to JSON converter, it only tells me the TOML is invalid. It doesn't tell me why, or what is wrong (the value should be quoted)

By comparison, this JSON linter identifies the issue (lack of a comma) and tells you what is expected, and where: