Dmitry

Great idea! 👍 It should really improve developer experience

Sorry, this case was not supported therefore lack proper testing. It will be officially released in next minor release

You can read your fields directly with useStore ```js const $user = createStore({name: 'alice', age: 22}) export const User = () => { const {name, age} = useStore($user) ... }...

Store is updated when it receives a value that is not equal (`!==`) to current one and to `undefined`, so component will rerender even with your `pick` function. But you...

New features are added to the library when there are enough feature requests from users, as almost every project is unique with its own unique demands, including updates by only...

Also, usually complex stores are composed from a simple ones with combine, so if you split your store and combine only required fields, then it will trigger rerender only when...

Split monolithic single store with irrelevant fields to atomic stores and [combine only necessary ones](https://github.com/effector/effector/issues/424#issuecomment-730616112). If your use cases assumes that you need more than one combination then just make...

```js const $partial = combine({qty: $qty, type: $type}) ``` You just don’t need any intermediate `$obj` store for that task. Even more, combine support arrays too: ```js const $qtyTypeTuple =...

Once again there is a problem with typings: there is not enough type tests for that method. This is important, for example we are able to merge sample with guard...

Thanks for reporting 👍 Behavior of such multi-way updates is one of the hardest part of forest implementation