next branch was too different to be merged directly into master. There were a number of bugs resolved in master but not next, and vice versa. Should look at next after this to see what bugs it addressed and make sure they are resolved again.
All this PR does is provide React 16.3 context based components to users. Please suggest API improvements as you see fit.
This PR also maintains backwards compatibility with the legacy context API. There are no breaking changes in this PR, so we don't need to do a 2.0 release just yet.
adrianmcli
commented
5 years ago
nextbranch was too different to be merged directly intomaster. There were a number of bugs resolved inmasterbut notnext, and vice versa. Should look atnextafter this to see what bugs it addressed and make sure they are resolved again.All this PR does is provide React 16.3 context based components to users. Please suggest API improvements as you see fit.
This PR also maintains backwards compatibility with the legacy context API. There are no breaking changes in this PR, so we don't need to do a 2.0 release just yet.