Skip to content

Conversation

taion
Copy link
Contributor

@taion taion commented May 6, 2016

  • Use separate context object
  • Use correct subscribe method

I'm putting this PR here ahead of pulling this out into a separate library just for the sake of visibility. This fixes a couple of my bugs in the original ContextSubscriber implementation. After this, I'll pull this out into a separate library.

@taion taion force-pushed the fix-context-subscriber branch from 47d7f90 to bd6b6a1 Compare May 6, 2016 22:40
- Use separate context object
- Use correct subscribe method
@taion taion force-pushed the fix-context-subscriber branch from bd6b6a1 to f78fd20 Compare May 6, 2016 22:40
@jquense
Copy link
Contributor

jquense commented May 6, 2016

👏 👍

this.unsubscribe = null
},

handleContextUpdate(eventIndex) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious: Why the method extraction?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No particular reason. Felt like I might as well take advantage of the autobinding in React.createClass.

@timdorr timdorr merged commit 8d10a89 into next May 7, 2016
@taion taion deleted the fix-context-subscriber branch May 7, 2016 07:51
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants