Is Room database the best approach for storing Tab data (Tab as an entity) ? Are there alternatives or best approach ?

In T353656#9593876, @YvesKalume wrote:

Is Room database the best approach for storing Tab data (Tab as an entity) ? Are there alternatives or best approach ?

Sure, since the rest of the project uses Room entities, this would make sense.

This seems like a big task for me as a newcomer. Perhaps I could start with a smaller issue to get acquainted with the codebase

This task will not remove the current limit on the number of tabs. That will be handled in a seperate task.

cooltey opened https://github.com/wikimedia/apps-android-wikipedia/pull/4985

Noting that so far cooltey estimates this has already been 9 points of work. And around 5 points amount of work remains.

Note on the current status of the work:

1. Tab database table to store a list of backstack IDs.
2. PageBackStack table to store the actual articles in the tab. The ID will be used in the Tab table.

Tabs screen

• Migration completed.

Article screen

• Upcoming refactoring needed:
  • Need to work on different tab action scenarios - open the article in: background tab, foreground tab, squash backstack items, current tab
  • Need to make sure only to query the current tab + backstack item for the article instead of keeping them in memory.
  • Need to make sure to handle the runBlocking vs proper coroutineScope for either tab count or tab commit actions.