Skip to content

Consolidate platform Track query implementation #15

Description

@zeevenn

What to build

Deepen the platform Track query Module so all Track list entrypoints share the same Track mapping, URL strategy, Artwork Reference strategy, fileSize handling, and Cursor pagination behavior. The all-Tracks, by-Artist, and by-Album paths should provide query criteria while the common Implementation owns result construction.

Acceptance criteria

  • Android all-Tracks and by-Artist Track queries reuse one Track mapping and resource strategy.
  • iOS all-Tracks and by-Artist Track queries reuse one Track mapping and resource strategy.
  • Paginated Track entrypoints reuse one Cursor pagination implementation per platform.
  • Invalid Android rows cannot cause a non-advancing cursor loop; the cursor always advances or the loop exits.
  • URL, Artwork Reference, cloud item fallback, and fileSize behavior are defined in one place per platform.
  • Tests or native-light fixtures cover Track mapping and pagination behavior without requiring repeated device-library setup where practical.

Blocked by

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions