-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Method to Get Old Index Path for New Index Path in Update #672
Comments
Is this the same as #546? |
It's like that issue, except for reloads rather than moves. |
We could probably look into adding that after #657 lands. This is similar to #297 as well. We can do this pretty easily w/out bothering to support @Adlai-Holler what sort of support are you thinking? |
Currently seems additive, so marking this for 3.1 |
Bumped this to new 3.5.0 milestone since 3.4.0 was released already. |
Nevermind, bumped to 4.0 since that's the next release. 😄 |
Bumping this to 4.1.0 since we don't have a need for this at Instagram right now. We would be happy to review and accept a PR if anyone wants to take this on. |
In https://github.com/TextureGroup/Texture we're looking to support using NodeControllers for each item, and having the NodeController survive across object updates (
reloadItemsAtIndexPaths:
) just like IGListSectionControllers do.Since IGListKit submits reloads as delete/insert pairs, I can't see any public way for us to find out whether, in a given batch update, an insert corresponds to a delete – if an item was updated.
@rnystrom @jessesquires Would you be willing to support that or point me in the right direction?
The text was updated successfully, but these errors were encountered: