React context official plans
Does anyone haved insight into or know how to find out the official plans and/or direction reagarding React
context? It's been well over a year of experimental use at your own risk status that wasn't even initially documented.
Without a full flux implementation (which may be overkill for some things) there really isn't a viable alternative for what context provides, so it would be nice to get some type of closure here! Some of us would sleep better at night knowing we wouldn't have to explain why we used experimental code to our bosses if the stuff hit the fan...
I had the same concern when first reading the docs.
But having looked through the react internals searching for
context related code. I found plenty of test cases and a relatively uncomplicated api for the
Seems to me the experimental label is more to avoid/deter the bypassing of the props and state react primarily focuses itself around.
But don't take just my word, look at how
context is used in react-redux and react-router.... I don't think will be fundamentally changing anytime soon.
- → Import statement and Babel
- → should I choose reactjs+f7 or f7+vue.js?
- → Uncaught TypeError: Cannot read property '__SECRET_DOM_DO_NOT_USE_OR_YOU_WILL_BE_FIRED' of undefined
- → .tsx webpack compile fails: Unexpected token <
- → React-router: Passing props to children
- → ListView.DataSource looping data for React Native
- → React Native with visual studio 2015 IDE
- → Can't test submit handler in React component
- → React + Flux - How to avoid global variable
- → Webpack, React & Babel, not rendering DOM
- → How do I determine if a new ReactJS session and/or Browser session has started?
- → Alt @decorators in React-Native
- → How to dynamically add class to parent div of focused input field?