Sova
Sova
@Drevoed Could you resolve conflicts please?
Looks awesome!
But I think there should be a local `route.$query` for each `createRoute` instance. If `route` is opened, `route.$query` should update in parallel with the global `$query`. If user updates `route.$query`...
```js onEnter({ route: somePage.route, target: loadFx }) ``` I think it is can work with fork API
You can load module via effect and track it with effector
I think this rule would be nice to add to a `strict` preset
@45m0d3u5 You can open an issue in patronum to add the `greedy` option
It would be useful in kind of `strict` preset
the committee decided it was useless
> a lot ESLint rules to define where developers should write their exports. It is not about "where" write exports, but about how to sort regular unit definitions and exported...