fix LocalDate use millis as default DateFormat, for issue #2477 Monster Yesterday 23:19 #2495
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.
What this PR does / why we need it?
Fixed the issue in the Fastjson v1 compatibility module where LocalDate deserialization defaulted to timestamp. This problem does not exist in both Fastjson1 and Fastjson2.
Summary of your change
Added the 'UseISO8601DateFormat' feature when generating the default DEFAULT_GENERATE_FEATURE. and wrote the corresponding test class. The default serialization of LocalDate, LocalDateTime, Instant, Date, LocalTime, OffsetDateTime, ZonedDateTime, and Calendar will all be affected.
Here are the date formats before the fix:
Here are the date formats after the fix: