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
Java has decided to use two different types for ISO 6801 durations:
The Duration type which parses the time portion of the spec (PT1D2H...)
The Period type which parses the date portion of the spec (PT1M)
This is the only language that does that as far as I'm aware and we're wrongly mapped the duration format from OpenAPI to Period which leads to parsing exceptions when we get a time portion.
Here is what needs to happen:
add a DurationAndPeriod composite type to the abstractions, make sure it implements temporalAmount, and comparable, as well as throws when both sub properties have a value.
update the parse node and serialization writer interfaces to use that type instead of Period, rename the methods adequately.
update the implementations to reflect the changes in interfaces.
update the java refiner to map to that new type instead of the Period type.
The text was updated successfully, but these errors were encountered:
Java has decided to use two different types for ISO 6801 durations:
This is the only language that does that as far as I'm aware and we're wrongly mapped the duration format from OpenAPI to Period which leads to parsing exceptions when we get a time portion.
Here is what needs to happen:
The text was updated successfully, but these errors were encountered: