Ensuring consistent indentation and preserving field order during YAML conversion. #675
Conversation
This file contains 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
2. Added a specific check for Node types since the JSON-first unmarshal was corrupting data without triggering an error. Signed-off-by: Souvik Kar Mahapatra <souvikat001@gmail.com>
1 task
Signed-off-by: Souvik Kar Mahapatra <souvikat001@gmail.com>
leecalcote
approved these changes
Feb 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR fixes #
Notes for Reviewers
Before:
ToYamlfirst unmarshalled tomap[string]interface{}and sincemapsin Go are unordered, we are losing out on the arrangement of the fields.After:
yaml.Nodeto preserve field order.next steps:
Signed commits