fix(formatter): handle nil JSON values - #14153
Open
zloglevel wants to merge 1 commit into
Open
Conversation
Signed-off-by: zloglevel <loglevel@outlook.com>
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.
What I did
Prevent
formatter.Printfrom panicking when JSON output receives an untyped nil value.reflect.TypeOf(nil)returns nil, so callingKind()on it panics;reflect.ValueOf(nil).Kind()safely returnsInvalidand lets the existing standard JSON path emitnull.Added regression coverage for both
jsonand legacy{{json .}}formatting. Both should producenull\n.Related issue
No issue; this is a small, self-contained nil-input fix.
(not mandatory) A picture of a cute animal, if possible in relation to what you did