Implement predictable JSON output #101
Merged
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
This change ensures that the JSON payload is generated in a predictable way. In particular it avoids random test failures because the expected output wasn't always matching. Signed-off-by: Simon Pasquier <spasquie@redhat.com>
Nexucis
approved these changes
Aug 13, 2025
Member
Nexucis
left a comment
Nexucis
left a comment
There was a problem hiding this comment.
I guess until we are adding something else than a string, we should be fine.
Thank you for this improvement @simonpasquier !
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change ensures that the JSON payload is generated in a predictable way. In particular it avoids random test failures because the expected output wasn't always matching.
I leaned towards using the
reflectpackage because I found no other alternative that wouldn't imply importing another library (like https://pkg.go.dev/github.com/google/btree or https://pkg.go.dev/rsc.io/omap) and a big refactoring.