Repository navigation
Preserve JSON null spelling in text and XML output - #31
Merged
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
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.
A parsed JSON null retains its native nil value but is formatted as the Go text
<nil>by InnerText and XML output. Use the JSON spellingnull, consistent with NodeNavigator.Value. Tests cover null versus the string "null", false and zero, round-trip the null node through encoding/xml, and confirm the native value remains nil.Validation at
d2f3d59604e97e3dac22a77198d3f060f2ae3663(base823396cf97c3b7cfc2fb3d2424a0ac49faf55aeb):go test ./... -count=1passes.go test -race ./... -count=1passes.git diff --checkpasses.Checks above ran locally on macOS; hosted CI and maintainer review remain separate. Prepared and independently reviewed with Codex assistance.