Win11 2023.11880 Pro License
Attached is an example file:
-
one COMP has an extension with a promoted attribute that is “exposed” in a custom param + has a promoted method
-
locking this component and copy-pasting it, or using in another project has no errors → can see the attribute and use the method
-
on the right side is the same component with the same extension, except the promoted attribute is not “exposed” in any way
-
copy pasting it reveals errors → cannot access the promoted attribute or method
It really makes me wonder which one is the correct behavior.
Could only find this discussion but not sure if there ever was a resolution to this.
My two cents to the matter, if it’s still relevant: I can see a reason why you wouldn’t want to expose an extension, but you can always package it one COMP deeper and lock the parent if needed, although this might not be the best UX design.
In my case I’d really like to use my extension from a locked component, so for now I’ll just “expose” something as a workaround — but need to know if this is future-proof!
LockedExtBug.toe (12.4 KB)