See also mobxjs/mobx-react#640
- [ ] separate
propTypesinto separate package - [ ] move
Provider/injectinto separate page
This release is not scheduled yet
Explanation: The reason why this is not done in mobx-react 6 is that it would create a snowball effect migration: "I want to upgrade to react 16.8 to use hooks" -> I need to upgrade to mobx-react 6" -> "Oh, now I need to refactor propTypes and provider / inject" .
So to keep the upgrade path friendly, let's separate these goals:
- mobx-react@6: Add support for hooks, increase minimum supported version to React 16.8
- mobx-react@7: Make mobx-react more lean and mean
mweststrate
>All comments
Are you sure that changing import is such a huge burden? As long as the API stays the same, it's pretty much fixable by _find and replace_ or a simple codemod.
Either way, I think that V6 should include deprecated messages and make those new packages now so people can actually start migrating and not to wait for V7 dropping a bomb :)
FredyC
on 22 Mar 2019
👍5
Was this page helpful?
0 / 5 - 0 ratings
Related issues
winterbe
路
34Comments
mweststrate
路
75Comments
FouMez
路
31Comments
arackaf
路
29Comments
mweststrate
路
35Comments
Most helpful comment
Are you sure that changing import is such a huge burden? As long as the API stays the same, it's pretty much fixable by _find and replace_ or a simple codemod.
Either way, I think that V6 should include deprecated messages and make those new packages now so people can actually start migrating and not to wait for V7 dropping a bomb :)