Progressive migration from redux: HOC #3539
Replies: 2 comments
-
You may actually try |
Beta Was this translation helpful? Give feedback.
0 replies
-
The first
…On Tue, 11 Oct 2022, 01:56 David Schontzler, ***@***.***> wrote:
We are looking at migrating a redux/saga codebase to mobx, for obvious
reasons. Since our codebase is quite large, we would like to do things
progressively, which means redux and mobx will be running together. We have
function and class components.
Are there any notes for this kind of set up? For example, when hooking up
to components, which HOC comes first?
// before: just redux 😔
export default connect(...)(SomeComponent);
// both: mobx + redux 🤨
export default connect(...)(observer(SomeComponent));
// or
export default observer(connect(..)(SomeComponent));
// future: just mobx 😍
export default observer(SomeComponent);
—
Reply to this email directly, view it on GitHub
<#3539>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN4NBBP3P3GNWW26K7E2WTWCSULVANCNFSM6AAAAAARBYSAGM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
schontz
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are looking at migrating a redux/saga codebase to mobx, for obvious reasons. Since our codebase is quite large, we would like to do things progressively, which means redux and mobx will be running together. We have function and class components.
Are there any notes for this kind of set up? For example, when hooking up to components, which HOC comes first?
Beta Was this translation helpful? Give feedback.
All reactions