Lifecycle callbacks should receive event arguments #1222
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
malarzm
force-pushed
the
gh902
branch
3 times, most recently
from
a3e42f7 to
b48417f
Compare
|
Rebased atop current |
malarzm
added a commit
that referenced
this pull request
Dec 14, 2015
Lifecycle callbacks should receive event arguments
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.
Closes #902
This PR contains a tiny BC break - before
preLoadlifecycle callback received$databy reference directly, now it receives aPreLoadEventArgsas it should BUT I wouldn't count it as BC break though - that event wasn't even documented.