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
I wanted to use formatter optional functionality to match dateTime e.g datetime("start", "yyyy-MM-dd'T'HH:mm:ss[.[SSSSSSSSS][SSSSSSSS][SSSSSSS][SSSSSS][SSSSS][SSSS][SSS][SS][S]]'Z'", Instant.now());
It looks like it should on provider side (checked by debugging matcher) but consumer is having problems and generates
Using this format I can parse String date with ranging from 2024-05-13T21:35:44 to 2024-05-13T21:35:44.123456789. The example is little extreme but the idea was to have a bit more flexible contract where Consumer doesn't care about milis so when Provider will start sending with precision 5 instead of 3 contract isn't broken
Hi,
I wanted to use formatter optional functionality to match dateTime e.g
datetime("start", "yyyy-MM-dd'T'HH:mm:ss[.[SSSSSSSSS][SSSSSSSS][SSSSSSS][SSSSSS][SSSSS][SSSS][SSS][SS][S]]'Z'", Instant.now());
It looks like it should on provider side (checked by debugging matcher) but consumer is having problems and generates
"start":"2024-05-13T21:35:44.801971000801971008019710801971801978019801808Z
Is this supported / am I doing something wrong?
Thanks!
The text was updated successfully, but these errors were encountered: