fix: Fix id alias columns typed as numbers. #1072
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stephenh
commented
May 4, 2024
| : FieldsOf<T>[P] extends { kind: "poly"; type: infer U extends Entity } | ||
| ? PolyReferenceAlias<U> | ||
| : never; | ||
| [P in keyof FieldsOf<T>]: P extends "id" |
There was a problem hiding this comment.
Put a special case here for "id" to get it flipped from a PrimiviteAlias<string> to EntityAlias<T>, which seems more accurate.
stephenh
pushed a commit
that referenced
this pull request
May 4, 2024
## [1.163.7](v1.163.6...v1.163.7) (2024-05-04) ### Bug Fixes * Fix id alias columns typed as numbers. ([#1072](#1072)) ([8d71cce](8d71cce))
|
🎉 This PR is included in version 1.163.7 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously the
idcolumn for like:The
idcolumn was typed asnumber, like the underlying database, instead of string to match our tagged ids.This was because of a mistake in the entity codegen generation of the
Fieldsinterface, just using the wrongidType.