Igor Kamyşev
Igor Kamyşev
Some operations in our application have lower priority than others, I purpose to add an operator to postpone event propagation until browser is idle. ```ts const $fitler = restore(fitlerChanged, null)...
Now `.navigate` and `.open` events push new state, in some cases it would be necessary to replace current state to prevent user from going back.
`$store.on` is less extendable than `sample`, and it could be replaced with `sample`. Let's add a rule to check this. In my mind, we should not add it to `recommended`...
Personally, I hate `restore` because of the following pattern 👇 ```ts const $currency = restore(currencyInited, null).on(settingsChanges, (_, { ccurency}) => currency); ``` Furthermore, I doubt that one line of code...
New `useUnit` has batching under the hood, so it is better to use single `useUnit` instead of `useUnit` for every store/event.
```ts sample({ source: { a: $a, b: $b } }) sample({ source: [$a, $b] }) ``` Object form is stricter, than tuple form because: + it is sustainable against order...
Forbid `$store.map` calls in react-render functions.
Additional config preset with #5 enabled by default.
[patronum/condition](https://github.com/effector/patronum#condition) is more clear way to write simple `split` with two cases. This rule will replace split-call with `condition-call`.
`useStoreMap` can use `keys`-parameter for memorize result. It passes this array to `React.useMemo` to skip unnecessary re-renders. We can write a rule to detect possible errors in `keys`. This rule...