Skip to content
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

fix: when using SET_INITIAL_DATE_IF_NULL in STJ only set MinValue if JSON value is null and runtime type is not nullable (#600) #602

Merged
merged 1 commit into from
Nov 20, 2024

Conversation

hf-kklein
Copy link
Collaborator

fix: when using SET_INITIAL_DATE_IF_NULL in STJ only set MinValue if json value is not nullable

i think, this was the initial intention behind the converters? and there's no older/existing test that fails, so I think it's fine that way

note that this does NOT change the behaviour of the newtonsoft converters!

Co-authored-by: Konstantin [email protected]

…f JSON value is null and runtime type is not nullable (#600)

fix: when using `SET_INITIAL_DATE_IF_NULL` in STJ only set MinValue if json value is not nullable

i think, this was the initial intention behind the converters? and there's no older/existing test that fails, so I think it's fine that way

note that this does _NOT_ change the behaviour of the newtonsoft converters!

Co-authored-by: Konstantin <[email protected]>
@hf-kklein hf-kklein merged commit 2f47e9b into v0.8.x-legacy Nov 20, 2024
9 checks passed
@hf-kklein hf-kklein deleted the nullable-date-v08 branch November 20, 2024 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant