Repository navigation
Conversation
Allow CodecOption (including EnableDecimalBinarySpecCompliantEncoding) to be used with the standard JSON full codec path, mirroring NewCodecWithOptions for Avro JSON. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Author
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.
Description
Adds
NewCodecForStandardJSONFullWithOptionsso callers can passCodecOption(includingEnableDecimalBinarySpecCompliantEncoding) when using the standard/internet JSON full codec path.NewCodecForStandardJSONFullnow delegates to the new helper withDefaultCodecOption(), preserving existing behavior.This mirrors
NewCodecWithOptionsfor the Avro JSON path and unblocks consumers (e.g. Dapr Kafka) that need both Standard JSON Full unions and opt-in spec-compliant decimal encoding.Issue Reference
Follow-up to #302 / v2.15.0.
Made with Cursor