docs(4-data-queries): document transform additive mode and in-place JSON parsing#222
Merged
Merged
Conversation
…SON parsing Clarify that adapter transforms run in replacement mode by default and flip to additive mode when any key is prefixed with + or -. Add a worked example showing how to decode a stringified JSON field in place using +field: "field|@ParseJson". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.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
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.
Summary
+/-keys = original event is discarded) vs additive mode (any+/-key flips the whole transform to additive, even when mixed with non-prefixed keys).+event_data: "event_data|@parsejson"to decode in place while preserving the rest of the event.Test plan
docs/4-data-queries/template-transforms.md#transforms,#custom-modifiers) resolve🤖 Generated with Claude Code