-
-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dateTime matcher optional support #1797
Comments
Why would you want to use such a format? Just give the max number of digits expected: 3 for microsecond precision and 6 or 9 for nanosecond precision. What you have given will provide the seconds fraction over and over. |
Using this format I can parse String date with ranging from |
taking into account the default serialization of Instant, i think this is relevant. |
Did you manage to find the answer @s1apped ? :) |
I've used this, seemed to work
|
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: