This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
provide original store slice state before in went through Tesler reducer as a reducer argument to allow overriding built-in behavior #588
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment there is no obvious way to override Tesler reducer reacting to built-in action:
tesler-ui/src/interfaces/store.ts
Lines 24 to 26 in 668d0d2
ClientReducer type provides
override
flag and it is in fact respected, but it is conceptionally flawed in a way that most projects treat slice reducer as a single function with a giantswitch
inside, so this flag will replace reducers for the entire store slice.This has absolutely no usage in real life and will be removed 2.0.0
Two other currently available options:
This PR provides client application reducer with additional argument:
originalState
, that contains the state of Redux store slice before it went through Tesler reducer: