-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StrictYAML #32
Comments
Ya send in the PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm the author of this library which was inspired by most of the same issues which inspired this website - for example the Norway problem. The overriding goal was to make it type-safe, which it is.
It doesn't solve 100% of the issues raised, and I still think that there are certain things it shouldn't ever be used for - e.g. deployment pipelines or anything else resembling a programming language, but it's 90% of the way there (still missing a nice, simple spec - one day I will get around to that).
I saw somebody mention it in one of the other issues and I was wondering if you'd be open to some sort of reference to it in the page or if it would spoil the one overriding message of avoiding YAML at all possible costs :)
The text was updated successfully, but these errors were encountered: