We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm not sure what exactly happens here, but I am comparing two JSON objects with ISO date formats that look like this:
2021-07-20T06:00:00.000Z
The code looks like this:
response.Should().BeEquivalentTo(JObject.Parse(apiResponseContent));
However, while the dates in response are kept, it looks like the dates in apiResponseContent are truncated, and become:
response
apiResponseContent
2021-07-20T06:00:00
The test therefore produces an error: JSON document has a string instead of a date at ...
Has anyone encountered this? Is it by design?
The text was updated successfully, but these errors were encountered:
I'm about to hit the sheets for today, but if you share a complete minimal runnable example I'll try to give it a look tomorrow.
Sorry, something went wrong.
I just ran into this same issue, when comparing two JObjects, did you ever find a solution @Ynhockey ?
JObject
@evilpilaf can you provide us with a minimal runnable example?
No branches or pull requests
I'm not sure what exactly happens here, but I am comparing two JSON objects with ISO date formats that look like this:
2021-07-20T06:00:00.000Z
The code looks like this:
response.Should().BeEquivalentTo(JObject.Parse(apiResponseContent));
However, while the dates in
response
are kept, it looks like the dates inapiResponseContent
are truncated, and become:2021-07-20T06:00:00
The test therefore produces an error: JSON document has a string instead of a date at ...
Has anyone encountered this? Is it by design?
The text was updated successfully, but these errors were encountered: