fix: types for model API with compound unique and findOne #1318
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.
This fixes the generation of the unique conditions interface for relationship fields.
As an example the following schema:
Currently produces a unique conditions interface for
Follow
that looks like this. Both not grouping thefrom
andto
fields into one object, but also using the wholeProfile
model as the type.With this fix the unique conditions interface is now this, which correctly groups the fields and uses the id's rather than the whole model.