You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current API with folding and aleady* flags is cumbersome. It is questionable how much composability it really offers. Maybe it would be better to simply allow each mixin to guide calling through getFirstMixin and getNextMixin (see #3). And maybe those methods should simply check the status of the DOM before doing anything. If they observe that DOM was already inserted, they do not do anything, for example. Or do it differently.
So in some way communication between mixins would work through node objects themselves. Similarly to how we communicate between event handlers by calling methods on the event object itself.
The text was updated successfully, but these errors were encountered:
Current API with folding and
aleady*
flags is cumbersome. It is questionable how much composability it really offers. Maybe it would be better to simply allow each mixin to guide calling throughgetFirstMixin
andgetNextMixin
(see #3). And maybe those methods should simply check the status of the DOM before doing anything. If they observe that DOM was already inserted, they do not do anything, for example. Or do it differently.So in some way communication between mixins would work through node objects themselves. Similarly to how we communicate between event handlers by calling methods on the event object itself.
The text was updated successfully, but these errors were encountered: