This repository has been archived by the owner on Nov 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 520
Support JSON in addition to YAML #15
Comments
I think you ment " And yes, would love json as the source of truth. But it's now 6 weeks after this issue, so i'm guessing this boat has sailed ... ⛵ |
No boats have sailed here! This project is just starting, and the last 6 weeks we honestly have been mostly working on documentation and paper cuts that people are running into, no major feature work besides core fundamentals (ex service discovery). |
woot! and cheers @spboyer for the PR. Respect, mate 👍 Respect to the entire team, actually 👍 |
I think @davidfowl will be really happy to see this closed. |
😄 |
Ok - so summary/answer is: YAML config only. No JSON config support. yes? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Some people have hate in their hearts for YAML. It's really cheap for us to support JSON as well as YAML, since YAML can be converted to YAML. https://github.com/aaubry/YamlDotNet/wiki/Samples.ConvertYamlToJson
Additionally, JSON has better support for schema/intellisense
We could do this by making JSON the source of truth and then converting YAML to JSON (always)
The text was updated successfully, but these errors were encountered: