-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block component and Block event adding is inconsistent #133
Conversation
I would say there should be a component container for each block, which is called |
Yeah. A On Mon, 29 Jun 2015 11:24 pm Chris Hobbs [email protected] wrote:
|
Should we do components.add or change block to have "on" function? I can make ComponentProvider extend EventBus. |
What? Why would componentprovider extend event bus? There just needs to be a component provider named components as a field for each block. |
@RX14 Agreed. Will work on this. |
TODO: #196 |
Current coverage is
|
Changed ComponentProvider to have component methods in the components instance variable
To add an event you use
events.on()
but to add components you don't usecomponents.add()
butadd()
. Small inconsistency, both things seem like a similar thing, but are done in a different way. Would be logical to have them both beadd()
andon()
or like the first line.