Use section and item keys for diffable collection identity - #217
Draft
michaelrhughes wants to merge 1 commit into
Draft
michaelrhughes wants to merge 1 commit into
michaelrhughes wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Diffable collections now identify items by their section and item keys, rather than displayed state. Rows with different keys can have equal state, and the same item key can appear in different sections. The public hashable-config initializers and table renderer are unchanged.
Content and style changes explicitly reload retained items without changing their identity; cell configuration reads the current row rather than a possibly retained snapshot payload. Snapshot construction also runs inside the existing exception boundary. Regression tests cover equal states, cross-section keys, content updates, insertion/deletion/movement, and duplicate-key exception handling.
All 132 tests pass using the package's SwiftPM scheme on an iPhone 17 simulator running iOS 26.5 with Xcode 26.6. The checked-in legacy Xcode project has no test action, so validation used its unchanged Package.swift and source/test directories through a generated SwiftPM scheme. No project or package configuration changes are included.