Closed bob2517 closed 3 years ago
After a lot of work with it in production, I'm finding it easy to remember the "&". Also, it's more obvious what needs to happen when adding a conditional to the event if there is already a "&" there specifying the target. So I'm closing this.
Internally assign &: to beforeComponentOpen and componentOpen type events so that developers don't have to remember to do this. These reserved events can only be used inside Active CSS components and they only ever apply to the component itself (&), so there isn't a need to have "&:" in developer code.
Just assign it internally when the parser spots those events. Leave it backward-compatible.
So the code will go from:
to: