After the initial groundwork on the DAO for userjs options, it should be straightforward to duplicate the DAO functionality to apply to collection page items, as described by the new database table that represents them.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Dbrant | T120114 [Mega-epic] Implement Reading lists (nee: collections) on Android. | |||
| Invalid | None | T120107 Synchronize user saved pages across devices. | |||
| Resolved | Dbrant | T127710 Implement migration path from old saved page list to new collection-based list. | |||
| Resolved | • Niedzielski | T127709 Implement DAO for reading lists. | |||
| Resolved | • Niedzielski | T127707 Implement new database table for Reading List lists | |||
| Resolved | • Niedzielski | T127708 Implement DAO for Reading List page items | |||
| Resolved | • Niedzielski | T127704 Implement new database table for saved pages, with collections in mind. |
Event Timeline
Comment Actions
I don't know how to test for this specifically, but exploratory testing such as the Reading lists of the current release (Wikipedia app 2.1.143-alpha-2016-4-14 on Samsung Galaxy) shows functional testing working as expected.