Decorator mutators for properties with same name on different entities are mixed up

[DaRosenberg]

Environment

No response

Reproduction

• Assume you have two entities A and B, both contain the property firstName: string.
• Add a mutator decorator for the firstName property on both entity classes
• In the mutator functions, add console.log("A") and console.log("B") statements so you can see which mutators execute and when

Describe the bug

If you add a mutator decorator for the firstName property on both entity classes, only one of them will run for both entities.

If you absolutely need a reproduction for this issue, let me know and I can try and create one, but I suspect that you will maybe already have an idea why it's happening. :)

Additional context

No response

Logs

No response

[CodeDredd]

Fixed via #2027 (will ship with v2.0.0). Decorator mutators were stored on a shared static of the base Model class keyed only by property name, so the last registered mutator for firstName won for all entities. Mutators (and casts + hidden fields, which had the same issue) are now scoped per entity.