Mateusz Burzyński
Mateusz Burzyński
You can write a function that would be able to interpret this. I dont see much value in supporting a syntax like this if it can be implemented in the...
That's really weird - have you tried reinstalling your whole node_modules?
Please always try to share a repro case in a runnable form - either by providing a git repository to clone or a codesandbox. OSS maintainers usually can't afford the...
Please always try to share a repro case in a runnable form - either by providing a git repository to clone or a codesandbox. OSS maintainers usually can't afford the...
It's not hardcoded - it only has a default value. You can call received `scrollTo` like this: ``` scrollTo(target, { duration: 1000 }) ``` `duration` can even also be a...
It's working fine - https://codesandbox.io/s/admiring-kalam-pxs9l . You have not actually used implemented `scrollToBottom` which is using duration option, but rather was using inline handler which wasnt passing any additional options...
Maybe but it's somewhat npm-specific (`overrides` is a field understood only by npm). The previous solution is kinda more general because for the most part the user should just swap...
> Looking at the docs of [MachineOptions](https://xstate.js.org/docs/packages/xstate-fsm/#machine-options) and it mentions only actions. This is a documentation of `@xstate/fsm` - it's a much simpler package and it only supports "configurable" actions...
I've tried to find one... and I couldn't (I could have missed it, but still...). The docs are currently introducing each concept separately and I didn't find a good "common"...
Not exactly. With `setup` you have to "provide" all implementations upfront - so you should never end up with missing implementations **but** you can still override/mock them afterward. This works...