Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Version used: 1.0.0-alpha5
Devices/Android versions reproduced on: n/a
A PagedList has access to the DataSource that we supply to page against. Admittedly, in the current PagedList implementation, that is buried under some wrapper layers.
Some DataSource implementations may require us to clean them up when we are done with them (e.g., to avoid garbage collection issues). When we are done with a PagedList, in many cases we are done with the DataSource backing that PagedList. It stands to reason that we should be able to retrieve our DataSource from the PagedList in order to be able to clean it up (e.g., call some close() method).
Thanks for considering this!