feat(java): add JSON date/time format annotation - #3908
Merged
Conversation
ayush00git
approved these changes
Aug 3, 2026
5 tasks
chaokunyang
added a commit
that referenced
this pull request
Aug 3, 2026
## Why? ## What does this PR do? ## Related issues #3908 ## AI Contribution Checklist - [ ] Substantial AI assistance was used in this PR: `yes` / `no` - [ ] If `yes`, I included a completed [AI Contribution Checklist](https://github.com/apache/fory/blob/main/AI_POLICY.md#9-contributor-checklist-for-ai-assisted-prs) in this PR description and the required `AI Usage Disclosure`. - [ ] If `yes`, my PR description includes the required `ai_review` summary and screenshot evidence or equivalent persisted links of the final clean AI review results from both fresh reviewers described in `AI_POLICY.md`, the Fory-guided reviewer and the independent general reviewer, on the current PR diff or current HEAD after the latest code changes. ## Does this PR introduce any user-facing change? - [ ] Does this PR introduce any public API change? - [ ] Does this PR introduce any binary protocol compatibility change? ## Benchmark
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.
Why?
Fory JSON date/time fields currently use only their built-in textual representations. Applications
need a field-owned way to select a deterministic
DateTimeFormatterpattern without registering acomplete custom codec for every occurrence.
What does this PR do?
JsonFormat(pattern = ...)annotation;Optional, arrays,Collection/List/Set,AtomicReference,AtomicReferenceArray, and Mapvalues;
conflicting representation annotations;
existing generated/interpreted codec capability path, writes without an intermediate String, and
parses ordinary ASCII input through the reader's reusable view;
Instantbehavior, and unsupportedcases.
Related issues
None.
AI Contribution Checklist
、
Does this PR introduce any user-facing change?
Benchmark