Mobx-react old behavior (before <StrictMode/>) #3794
Replies: 1 comment
-
In that case I recommend to stick to the current mobx-react version.
…On Sun, 12 Nov 2023, 10:53 Andrey Skripko, ***@***.***> wrote:
Is it possible to make the behavior that was disabled in mobx-react due
to ***@***.*** <StrictMode/> (when props & context became reactive)
configurable? I would prefer to include the old behavior, since we have a
lot of functionality tied to it.
—
Reply to this email directly, view it on GitHub
<#3794>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN4NBC7CLB2B76I5GZ6REDYECMB3AVCNFSM6AAAAAA7H4UDIKVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZVHA2DANJXGM>
.
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
1tu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is it possible to make the behavior that was disabled in
mobx-react
due toReact@18 <StrictMode/>
(when props & context became reactive) configurable? I would prefer to include the old behavior (and don't use<StrictMode/>
), since we have a lot of functionality tied to it.Beta Was this translation helpful? Give feedback.
All reactions