Skip to content

Modularize Spotify page controller logic #10

Description

@postigodev

Summary

Spotify logic is one of the richest parts of the app: auth flow, polling, playback actions, target-device selection, and session rendering.

Why this matters

This code works, but it is still concentrated enough that it raises the cost of changing one area without understanding all of them.

Expected outcome

Split Spotify page/controller logic into smaller pieces while preserving:

  • active-view-only polling
  • no duplicate intervals
  • no stale target-device behavior
  • current UI behavior

Likely files

  • apps/tauri/src/main.ts
  • apps/tauri/src/pages/spotify.ts
  • apps/tauri/src/features/*

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    frontendTypeScript frontend workhelp wantedMaintainer would welcome contribution hererefactorInternal cleanup or modularization workspotifySpotify auth, routing, or playback logic

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions