awesome-lint
json5
| awesome-lint | json5 | |
|---|---|---|
| 2 | 94 | |
| 590 | 6,301 | |
| - | 0.9% | |
| 7.2 | 0.0 | |
| 4 months ago | 5 months ago | |
| JavaScript | JavaScript | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
awesome-lint
-
Potherca's Weekly Github Stars - 2020 Week 25
What I mean by versionless, is that this Action allows consumers to specify the version of the awesome-lint package they desire.
-
Prefer the English Style of Quotation Mark Punctuation over the American
I tried to implement some linting rules for quotation mark and punctuation once. Took me way too much time and effort. It's mostly trial and error but good enough I guess to highlight the most blatant abuses.
Anyway, here is the code: https://github.com/sindresorhus/awesome-lint/pull/101/files
json5
- JSON5 – JSON for Humans
- Why the fuck are we templating YAML? (2019)
-
I pre-released my project "json-responder" written in Rust
JSON5 support
-
topoconfig: enhancing config declarations with graphs
Meanwhile, formats have been evolving (JSON5, YAML), config entry points are constantly changing. These fluctuations, fortunately, were covered by tools like the cosmiconfig.
-
That's a Lot of YAML
I think JSON5 is fairly close to this: https://json5.org
I reckon the only thing it's missing to be truly accessible to non-techies is that string values still need to be quoted, i.e. you can't have:
key: this is my value
(I'm definitely not saying it would be a good idea to allow quotes to be dropped, just that that's the only potential stumbling block I see for non-techies.)
-
XML is better than YAML
I believe that's JSON5.
https://github.com/json5/json5
It's my preferred configuration file format, it fixes all the problems I have with JSON (trailing commas, comments) without turning it into a mess full of gotchas like YAML.
- Fx – Terminal JSON Viewer
- What Is Wrong with TOML?
-
🚀 'GET' API in API Maker
JSON 5 support
-
TySON: a native go library that lets you use TypeScript as an embedded configuration language without depending on Node or V8
I would like to see mention of JSON5 which is 11 years its elder. For comments in JSON, JSON5 is a good starting point.
What are some alternatives?
lockfile-lint - Lint an npm or yarn lockfile to analyze and detect security issues
Json.NET - Json.NET is a popular high-performance JSON framework for .NET
nano-staged - Tiny tool to run commands for modified, staged, and committed files in a GIT repository.
hjson-js - Hjson for JavaScript
data-transfer-project - The Data Transfer Project makes it easy for people to transfer their data between online service providers. We are establishing a common framework, including data models and protocols, to enable direct transfer of data both into and out of participating online service providers.
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
starred - creating your own Awesome List by GitHub stars!
toml - Tom's Obvious, Minimal Language
github-action-awesome-lint - GitHub Action for awesome-lint where you specify the package version!
jsonnet - Jsonnet - The data templating language
stylelint - A mighty CSS linter that helps you avoid errors and enforce conventions.
sublime-hjson - Hjson support for Sublime Text