-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for reload instead of delete+insert #60
Comments
It maybe reasonable implementing a |
I think that the best solution is for the API's user to change the way she calculates the sectioned values so a change to the details of an item are reflected and treated as a deletion + insertion. |
I have a problem with this as well. Here is a use case example.... I have cells that include some time interval display (something like: "updated x seconds ago") and a button/tag that can be toggled in other parts of the app as well. When the user uses pull to refresh the new content is loaded and tableview is updated using |
I'm exploring using a different animation for reloading a row, for that I would need Dwifft to call
reloadItems
instead ofdeleteItems
andinsertItems
.My first guess is that a adding a naive support for reloads would just require checking for the intersection between deletes and inserts in
processChanges(newState:diff:)
.What do you think?
The text was updated successfully, but these errors were encountered: