You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 17, 2019. It is now read-only.
To make the team's life easier, there is a need for a place, where local data can live and can be propagated to any components in the tree, no matter how deep those components are. This seems to be the perfect use case of React Context.
Things to consider:
implement connection between Store context, and Service Worker
Expected Behavior
There should exist a Context Provider, (called Store) that holds all data used throughout the app in its state.
Furthermore, there should exist a Consumer (via withStore HOC and/or use of static ContextType)
Areas affected
frontend
backend
Priority
As fast as possible
Size
Probably everybody will make use of this, but the setup process is relatively easy and can be done by one person.
The text was updated successfully, but these errors were encountered:
To make the team's life easier, there is a need for a place, where local data can live and can be propagated to any components in the tree, no matter how deep those components are. This seems to be the perfect use case of React Context.
Things to consider:
Expected Behavior
There should exist a Context Provider, (called
Store
) that holds all data used throughout the app in itsstate
.Furthermore, there should exist a Consumer (via
withStore
HOC and/or use of static ContextType)Areas affected
Priority
As fast as possible
Size
Probably everybody will make use of this, but the setup process is relatively easy and can be done by one person.
The text was updated successfully, but these errors were encountered: