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.
What?
Add type support for return value when select is used. Instead of returning the
string | Relation
in to-one relations and(string | Relation)[]
not proper type is returned -Relation
orRelation[]
for cases when the relation is explicitly selected.NOTE1: string can be replaced with number, depends on the IDs you use in your app
NOTE2: Relation is a collection type
Why?
Because it is frustrating working with union types when you know that in runtime you will have this typing
How?
I have expanded
TransformDataWithSelect
type.Type checking is done using a type utils
Equal
that resolves totrue
if types are same andfalse
otherwise. We type a variable with this and assigntrue
to a variable. If type resolves tofalse
you get an error.Should I add type checks in every test case?
Future works?
depth
.