-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configure enforceActions does not work! #1680
Comments
I guess |
That's not true as it was stated:
If it is not a bug, I guess that feature just doesn't work with |
When filing a bug, please describe expected and observed behavior, as
prescribed by the issue template. Reading this conversation it is still
unclear for me what "doesn't work" means in this conversation. Since I
don't see observed observables in your example, I think you might be
misinterpreting the docs @kuitos quoted.
Op ma 13 aug. 2018 om 15:33 schreef U.P <[email protected]>:
… That's not true as it was stated:
In sloppy (true) mode, MobX will only throw if an observed observable is
modified, in "strict" mode it will even throw for non-observed observables
If it is not a bug, I guess that feature just doesn't work with production
build as well as umd version cuz it has meaning only in developing phase.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1680 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABvGhAOT03hKu9Fwf4g3sWCqD9FcUtRvks5uQYAQgaJpZM4V54v9>
.
|
I did assign
|
In sloppy (true) mode, MobX will only throw if an observed observable is modified, in "strict" mode it will even throw for non-observed observables Maybe not the most optimal formulation (PR welcome!), but in other words, in |
Not sure if relevant, but some time ago I proposed perhaps a bit more matching/self-explanatory nomenclature: |
In MobX 4.4 / 5.1 the config values have changed to |
I was using
umd mobx 5.0.3
and I couldn't getconfigure({ enforceActions: true })
works. It just does nothing. There is no error thrown because of changing observable object outside of an action.Could anyone take a look into my sample code to see where is my problem here? Otherwise, it might be a bug, isn't it? Thank you.
https://codepen.io/up209d/pen/KBENbz
The text was updated successfully, but these errors were encountered: