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
Custom date formats are a super common "feature" of the real world, and mapping APIs to the real world, particularly with custom date formats is a pain point with OpenAPI.
There's a few ways we can go about implementing this, but having a coherent story that is easily implemented in each platform would be great.
A couple of ideas have been proposed:
Using a custom format with formatting string as a parameter, like custom-date(mm-yyyy-DD), though this introduces parsing complexity
Using a custom field along side a well known custom format, such as:
Custom date formats are a super common "feature" of the real world, and mapping APIs to the real world, particularly with custom date formats is a pain point with OpenAPI.
There's a few ways we can go about implementing this, but having a coherent story that is easily implemented in each platform would be great.
A couple of ideas have been proposed:
format
with formatting string as a parameter, likecustom-date(mm-yyyy-DD)
, though this introduces parsing complexityBoth have their pros and cons.
The text was updated successfully, but these errors were encountered: