This repository has been archived by the owner on Sep 7, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 248
Consider dropping the usage of React context #304
Labels
Comments
Is there reference about why react-router drop it ? |
remix-run/react-router#2646 in the middle of the desc. |
I saw that they're moving multiple contexts into 1. Not dropping it entirely. |
Yeah but I am pretty sure we can do without those. Context is handy but not the silver bullet and make functional component not that functional :D |
Oh. I have to agree with you about this. It's hard to test component with context. |
This should close #40, right? |
We should indeed, remove redux AND remove explicit context in favor of provider components. |
Closed
Going to be fixed with #925 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
react-router did it.
Props should be enough. We should at least evaluate the idea, to make things (and tests) simpler.
I want a minimal API and context make things more complicated (no big deal but still).
The text was updated successfully, but these errors were encountered: