feat: Stateful Components #3960
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It may be worth just having one PR for these changes rather than having #3959 too. Adding the stateful mixin doesn't seem like that big of a change here. |
|
I split it up at @gkatsev's request. Feel free to duke it out with him. 😛 |
misteroneill
force-pushed
the
stateful-component
branch
from
e741b90
to
f2ae875
Compare
gkatsev
approved these changes
Jan 26, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The PR for advanced plugins introduced the concept of mixins and added two: evented and stateful.
This PR follows #3959 by providing
Components with the benefits of the stateful mixin.Requirements Checklist
Docs/guides updatedExample created (starter template on JSBin)