5 ms·
Not sure if serious, but this update swaps out the internals without affecting users/developers, the API is fully backwards compatible
by cheapsteak 9y ago
Not sure if serious, but this update swaps out the internals without affecting users/developers, the API is fully backwards compatible
- flukus 9y agoNo API changes doesn't mean that your code will work 100% as it was before.
- b34r 9y agoIt's actually not. There are some lifecycle changes, potential modifications to setState (async only), etc. That's why it's being released as a new major version.
- cheapsteak 9y agoI think we may be splitting hairs over the definition of API compatibility
- antjanus 9y agoit's one of those 99% compatible except for a few small quirks that only developers using it on large applications will notice. The React devs have also been great with releasing codemods for breaking APIs.
- danabramov 9y agosetState is not async-only in React 16. We keep the old behavior and just change the engine now. Later we will look into enabling new behavior.