fix(core): handle BigInt in date hydration #7003
Merged
+78
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #7002
This PR adds support for
BigIntvalues inDatehydration. This is particularly useful when using drivers likebetter-sqlite3withsafeIntegers: trueenabled, which returns integers asBigInt.The hydration logic generated by
EntityComparatorhas been updated to explicitly handletypeof value === 'bigint'. It now converts theBigIntvalue to aNumberbefore parsing it as a date, ensuring that timestamp values returned as BigInts are correctly hydrated into Date objects.Dependencies
I have submitted a PR to Knex to support the option(
defaultSafeIntegers: true) for thebetter-sqlite3driver to return bigints (see knex/knex#5050). Testing this change will be possible once that Knex PR is resolved.Changes
EntityComparatorto include a check forbiginttype in the generated hydration code for Date properties.bigintis encountered, it is converted toNumberusingNumber(value)before being processed byparseDate.Related Issue(s)
Tests