Mikael Couzic
Mikael Couzic
Currently, it is possible to sort using the key of an item, but only through the `Comparator` and `ComparatorFactory` interfaces, for example: https://github.com/winterbe/sequency/blob/7be941df1dce7c5ad50df60c1ddec72b46a54b54/test/sorted.test.ts#L67 https://github.com/winterbe/sequency/blob/7be941df1dce7c5ad50df60c1ddec72b46a54b54/test/sorted.test.ts#L89 https://github.com/winterbe/sequency/blob/7be941df1dce7c5ad50df60c1ddec72b46a54b54/test/sorted.test.ts#L108 https://github.com/winterbe/sequency/blob/7be941df1dce7c5ad50df60c1ddec72b46a54b54/test/sorted.test.ts#L135 The goal of this...
```ts store.computeFromPath(['a', 'b'], b => ...) ```
```ts .computeFromField('data', data => { if (data === undefined) return {}; return { computedValue: 'whatever }) ```
```ts store.changeDetectionStategies({ myValue: (previousValue, nextValue) => previousValue.myField === nextValue.myField }) ``` Since this case is so common: ```ts store.changeDetectionSelectors({ birthDate: _ => _.getTime() }) ```
Hide store reference behind proxy LightStore instance
`currentState` should hold all readonly fields
... especially since it's already documented !!!
calling `.pluck('optionalField')` causes a compilation error, while it should be legal