This repository has been archived by the owner on Mar 20, 2022. It is now read-only.
Give assignEntity access to the original input object #72
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.
Problem
When using
assignEntity
, we need to build values based on information from multiple keys/entities in the original input tonormalize
.Why do this here? When reading from a state happens more often than writing, it's much better to have this done once on receipt than every time it's accessed.
Solution
Change
assignEntity
to be given a fourth argument, the value of the original, non-normalized object.Resolves #64