move keyed each diffing into a shared helper #1256
Merged
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.
This is a follow-up to both #1249 that starts to make good on the promise of #1173. It moves the logic for updating a keyed each block into a shared function.
While this does mean that a standalone component with a keyed each block will become slightly larger (because the function needs to accommodate e.g. blocks with and without transitions), there are substantial benefits in return: an app with two or more keyed each blocks will shrink (in terms of filesize, startup time and memory usage), and performance should improve because the function will warm up quicker if it's called from multiple places.
Granted, this is all fairly obvious from the point of view of a traditional framework.
An equally big win, in my view, is that the codebase itself becomes somewhat simpler and easier to reason about.