What's Changed?
| v5.0.0 | |
|---|---|
| 1. | Converted to full Typescript. |
| v4.7.0 | |
| 1. | store.setState can now accept an array of updates for gurranteed orderly processing. |
| v4.6.0 | |
| 1. | store.resetState can now update reset current state even when initial state does not exist. Formerly, a resetState call on a non-existent initial state had no effect. |
| v4.5.0 | |
| 1. | Tags to update non-existent state slices are now recognized. Previously, they had resulted in no-ops. From now on, they will result in new default slices matching the result of the given tag operation. |
| v4.4.0 | |
| 1. | Returns undefined for selector map pointing at a non-existent state slice. (Previously returned null). |
| v4.3.0 | |
| 1. | Added React.Ref forwarding to connected hoc client components. |
| v4.1.0 | |
| 1. | Added new setState tags to facilitate state update operations. |
| 2. | Added negative indexing capabilities. |
| 3. | Exposing the store via its Context Provider ref attribute. |
| 4. | Exporting crucial constants such as @@STATE and setState tags such as @@CLEAR, @@MOVE etc. |
| v4.0.0 | |
| 1. | Added the connect function to facilitate the encapsulated context-usage method. |
| 2. | Added stronger support for deeply nested state structure. See store.setState |
| 3. | Replaced the useContext watchedKeys array parameter with a selectorMap object. |
| 4. | Removed the necessity for direct store subscription. |
| 5. | store.resetState can now take a property path array targeting which state slices to reset. |
| 6. | Context provider accepts an optional storage prop for memorizing initial state. |
| 7. | Removed the need for store.getState. store.data now holds the state slices used at the client. Changes in any of the slices held by the store.data are automatically updated as they occur. The client is immediately notified of the update. |