You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many ParamConverters assume a default String representation for a specific Java type. Right now, we've standardized on ISO-8601 for Date, Time and Timestamp formats which aligns with the new Java Date/Time library. In the event we have to process other String representations, we should have the ability to customize these converters - two annotations immediately come to mind but there may be more:
@FormatString - Allows the user to specify an alternate format string (for conversions that accept one) or to specify the format string for conversions that require one.
@DefaultTimeZone - Allows the user to specify the time zone to be used if one is not included with the ISO-8601 compliant string. This allows what would otherwise be LocalDateTime objects to be Instant or ZonedDateTime.
The text was updated successfully, but these errors were encountered:
Many
ParamConverter
s assume a defaultString
representation for a specific Java type. Right now, we've standardized on ISO-8601 for Date, Time and Timestamp formats which aligns with the new Java Date/Time library. In the event we have to process otherString
representations, we should have the ability to customize these converters - two annotations immediately come to mind but there may be more:@FormatString
- Allows the user to specify an alternate format string (for conversions that accept one) or to specify the format string for conversions that require one.@DefaultTimeZone
- Allows the user to specify the time zone to be used if one is not included with the ISO-8601 compliant string. This allows what would otherwise beLocalDateTime
objects to beInstant
orZonedDateTime
.The text was updated successfully, but these errors were encountered: