Incompat: metadata annotations from inherited sub classses added to top level class
Description
This is a compatibility bug exposed by the Util Test in Coldbox.
You have an inheritance chain of target -> class1 -> class2 -> class3
However, the top level target receives ALL the annotations from the chain. Thus several tests are failing, since it is not expecting those annotations to exist there.
Attachments
1
Activity
Show:
Luis Majano October 28, 2024 at 12:18 PM
Hmm I did not see a bug on this yet. So I am assuming it's working as is. Will have to check more of our tests
Brad Wood October 25, 2024 at 8:53 PM
What about properties? Should those be merged? That’s pretty important for getter and setter stuff to work for the concrete class to know about all the properties. In other words, do properties from the base class show in the metadata of the child class’s metadata? That one is a little fuzzy for me since actual property values are stored in the variables scope, which IS merged between parent and child. Plus, generated getter/setters all need to exist on the child class, even if the property in question came from the parent.
Luis Majano October 22, 2024 at 4:26 PM
FYI, this is a blocker for certification
Fixed
Pinned fields
Click on the next to a field label to start pinning.
This is a compatibility bug exposed by the Util Test in Coldbox.
You have an inheritance chain of
target -> class1 -> class2 -> class3However, the top level
targetreceives ALL the annotations from the chain. Thus several tests are failing, since it is not expecting those annotations to exist there.