gookit/config
json5
| gookit/config | json5 | |
|---|---|---|
| 3 | 94 | |
| 522 | 6,301 | |
| 0.4% | 0.7% | |
| 7.7 | 0.0 | |
| about 2 months ago | 5 months ago | |
| Go | 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.
gookit/config
-
topoconfig: enhancing config declarations with graphs
gookit/config
-
How to read .env file with a variable that contains $ ?
In that case, you should not be using the shell to read the .env file; instead, use a library. I recommend https://github.com/gookit/config
- GitHub - gookit/config: 📝 Go configuration manage(load,get,set,export). support JSON, YAML, TOML, Properties, INI, HCL, ENV and Flags. Multi file load, data override merge, parse ENV var, binding data to struct.
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?
viper - Go configuration with fangs
Json.NET - Json.NET is a popular high-performance JSON framework for .NET
go-env - Golang handling of environment values
hjson-js - Hjson for JavaScript
konfig - Composable, observable and performant config handling for Go for the distributed processing era
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
gcfg - read INI-style configuration files into Go structs; supports user-defined types and subsections
toml - Tom's Obvious, Minimal Language
ini - Package ini provides INI file read and write functionality in Go
jsonnet - Jsonnet - The data templating language
toml - Instream TOML to JSON encoder
sublime-hjson - Hjson support for Sublime Text