Keeps views automatically in sync with state. Unobtrusively. https://egghead.io/courses/manage-complex-state-in-react-apps-with-mobx
useObserver has its own tradeoffs you will probably discover later
but you need ask over at Enzyme what they don't like about it
But thanks for your support and reply :) it was really helpful to my team :)
Looking into xstate and mobx, I've found a demo on codesandbox that uses
that function is not documented, but it is exported. Is it safe to use?
https://github.com/mobxjs/mobx-utils/search?q=fromStream&unscoped_q=fromStream
fromStream from mobx-utils howeverthat function is not documented, but it is exported. Is it safe to use?
https://github.com/mobxjs/mobx-utils/search?q=fromStream&unscoped_q=fromStream
another cool feature of ChronoGraph, something to support in Mobx too? shorturl.at/cwxLY
With inferred properties it would be really elegant. No constructor necessary
Also annotating fields could happen as
static property
Looks nice actually
const { makeAutoObservable, autorun } = require('mobx');
const Doubler = (value) => makeAutoObservable({
value,
get double() {
return this.value * 2
},
increment() {
this.value++
}
})
const doubler = Doubler(1)
autorun(() => {
console.log(doubler.double)
})
doubler.increment()
also nice
maybe makeAutoObservable could accept function and automatically make class from it
because class instances are far less expensive in JS (methods are on prototype, not on object)
@sheerun_gitlab declaring members and making them observable is exactly what
observable(obj) already does. As far as creating a function that generates a class goes, I don't see any benefit of that above just declaring a class :) achieves the same thing, without confusing transformations, allowing statics, instanceof checks etc.
function implementations can be shared without classes as well, just hoist them
I am trying out mobx state tree, is this the right place to ask about a typescript related error I am seeing with the Mobx
I was playing around created a small app that retrieves values from a map and renders them to do list start and the types for
values function?I was playing around created a small app that retrieves values from a map and renders them to do list start and the types for
values seem like they might have a problem?
@mweststrate Indeed, following works too. Awesome
class Doubler {
constructor(value) {
this.value = value
}
get double() {
return this.value * 2
}
increment() {
this.value++
}
}
const doubler = makeAutoObservable(new Doubler(2))
autorun(() => {
console.log(doubler.double)
})
doubler.increment()
Thanks, I'll see if we can investigate further, it seems when running a headless browser the render does not happen but does when using a full browser. Is there any minimum browser config that is required for mobx renders to occur.
Thanks for the help on this one, turned out to be an issue with a vpn.
This is probably a question with an obvious answer, but why do onBecomeObserved and onBecomeUnobserved support all observable types except objects? I'm trying to do something like this and I'm struggling:
const tokenDetails = observable({ token: null, expiryMs: null })
onBecomeObserved(tokenDetails, () => { ... })
onBecomeUnobserved(tokenDetails, () => { ... })
Hi Mobx-nation!
I've just accomplished a proof of concept yet another model library for Mobx :)
It's a tiny helper for TS users who likes the class approach and doesn't need the full power of MST or keystone.
Also it's battle-tested. We built a huge app using the JS version. But TS version was just baked :)
Feedback is welcome 🙏
I've just accomplished a proof of concept yet another model library for Mobx :)
It's a tiny helper for TS users who likes the class approach and doesn't need the full power of MST or keystone.
Also it's battle-tested. We built a huge app using the JS version. But TS version was just baked :)
Feedback is welcome 🙏