YAML Support #10
Open
YAML Support #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don't really have a use for this, but it was a fun exercise.
Original motivation is/was to use it for a simple config file (i.e. a "light" version of a HOCON/Typesafe Config, but without all of the glue-code that would be required to create the config)
It could also be useful if we ever need to pragmatically generate or read kubernetes yaml files, Amazon Serverless configs (https://serverless.com/framework/docs/providers/aws/guide/serverless.yml/) Although, I believe Amazon also has JSON support for many of those things.
I want to say the existing fm-serializer tests are REALLY good. Having such good test coverage really helped isolate any issues in the implementation.