feat: add association decorators #15483
Merged
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.
Pull Request Checklist
Description Of Change
This is part of #15334
This PR adds decorators
@BelongsTo
,@HasMany
,@HasOne
, and@BelongsToMany
.Their signature is not identical to the one from sequelize-typescript:
@ForeignKey
decorator was only ever used as a way for the above 4 decorators to guess which attribute was the foreign key. From experience, this ended up being more confusing than helpful. I have not included it in my implementation. Instead, users are required to specify theforeignKey
parameter in@BelongsTo
,@HasMany
,@HasOne
, and@BelongsToMany
.@BelongsTo
,@HasMany
, and@HasOne
: All of them check that the foreign key has been defined (in type) on the proper model@BelongsToMany
have been dropped except one. They were all too difficult to read. The only remaining signature is@BelongsToMany(target, options)
This is the last PR that was really essential to make the decorator system usable. The remaining 5 decorators are shortcuts