Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
|
Thanks! Technically correct but I'm going to close this in favor of #15849. |
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.
Fixes #15832
Since #15540, a
Valuewrapping null stops the modifier chain before the modifier runs, so{{ empty_field | to_json }}renders nothing instead ofnull. Inside a JSON template that leaves invalid JSON like{ "items": }.This adds
to_jsonand itsjsonalias to the null-aware modifiers list from #15782, next tobool_string.One thing to note: the list applies to bare and missing variables too, so
{{ missing | to_json }}now outputsnullas well. It output nothing even before #15540, butnullseems like the right answer for a JSON modifier, and it matches what #15782 did forbool_string.🤖 Generated with Claude Code