-
Notifications
You must be signed in to change notification settings - Fork 47k
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
Stop masking context #9266
Comments
This could also be used in the case where you ReactDOM.render inside a component and want to preserve things like the redux store and react-router. |
That's a great point @brigand! Passing, cloning, or even serializing the context data could benefit from this feature. |
We'll be changing how context works, and I don't think properly exposing it in That said we'll probably get rid of masking so I'll hijack this issue to track it. |
I don't know what that means, but as long as I can prevent wasted renders based on props, state and context I'm a happy camper. If this is something that can automatically be handled by |
The proposed context API solves this (reactjs/rfcs#2) and we don't plan changes to the existing one so I think this is not relevant anymore. |
Feature
Return all contextProps available via a wildcard prop, this would be helpful for those who want to do
shouldComponentUpdate
comparisons with props, state, and context.Possible solutions
The text was updated successfully, but these errors were encountered: