-
-
Notifications
You must be signed in to change notification settings - Fork 5
Context best-practices #34
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
Conversation
Found these articles you mentioned the last time quite useful. Probably worth a mention in the guides as well: |
Sounds good. Brainstorm time. :) I was thinking of these "one-time-fetch" scenarios the other day. Using contexts makes sense but I still feel like it's an overkill if the data is not consumed by multiple components. The other workaround I could think of is making use of
It comes with the cost of a somewhat more complex logic(e.g. each time a certain component mounts we should check for the data's existence) but it's worth the "effort" imo. Could you perceive other advantages/disadvantages? |
Why are contexts an overkill though? |
Forget the proposal above, it seems it's indeed one of the best-practices of using contexts.
|
Closing in favor of ca945f6 and c-hive/basics#8 Thanks for gathering use cases in this PR! |
Looking for ideas..