3 ms·
I've had some problems with mobx. Works great on smaller projects, but can be hard to debug when something goes wrong. Observable objects are tough to read in
by tarr11 9y ago
I've had some problems with mobx. Works great on smaller projects, but can be hard to debug when something goes wrong.
Observable objects are tough to read in the debugger.
The main gotcha I found [1] was dereferencing property of an observable didn't trigger rendering. Didn't feel very intuitive to me.
Also, occasionally, I would insert a row into an observable array and nothing would happen, and I could never figure out why.
Using redux now, it's more explicit and full of boilerplate and ceremony, but I understand all the code, and there is far less magic.
[1] https://mobx.js.org/refguide/observer-component.html https://mobx.js.org/refguide/observer-component.html
- disease 9y ago>dereferencing property of an observable didn't trigger rendering For real!? This seems like either a critical bug or huge design mistake on the part of the MobX author. I also cannot understand why you cannot make a Set an observable. It's such a fundamental part of programming!