This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been musing about #1437 recently. This is a prototype for a possible context-based state management framework we could use to address our prop-drilling woes.
My specific goals for this are:
.debug()
output.API
Here's a draft of the initial API that I've come up with:
And on the provider side:
Remaining
c.observeModel()
.External factors
static contextType
yet, but it's underway. See Shallow API setContext should work withoutstatic contextTypes
for React 16 enzymejs/enzyme#1913 and Complete React 16 support enzymejs/enzyme#1553.