fix(typescript): infer nullable INTERVAL columns as string | null #1031
+256
−2
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.
Fixes #1030
Problem
When generating TypeScript types, nullable
INTERVALcolumns are currently inferred asstringinstead of
string | null. This breaks type safety because the database allowsNULLvaluesbut the generated types do not reflect that.
Changes
is_nullableforINTERVALcolumnsINTERVALfields are typed asstring | nullResult
Developers now get accurate TypeScript types that match the database schema,
preventing runtime null issues and improving overall type safety.