fix(core): ensure propagation and change-tracking when useDefineForClassFields
enabled
#4434
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.
Propagation on new entities you create via constructor are supported too, by modifying the entity class prototype, but this technique fails when
useDefineForClassFields
TypeScript compiler flag is enabled (which is true when targetingES2022
or higher). You can get around this by usingdeclare
keyword in your entity definition, or by creating entity instances viaem.create()
, which will ensure the propagation is enabled.Related #4216