[GH-ISSUE #193] Handle multiple copies of a single track in the same pool #124

New issue

Closed

opened 2026-02-27 19:16:57 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 19:16:57 +03:00

Owner

Originally created by @EddieTheCubeHead on GitHub (Apr 6, 2024).
Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/193

Originally assigned to: @EddieTheCubeHead on GitHub.

Backend and frontend should switch to communicating about pool members with pool member id instead of uri, as a single track can be a part of multiple users' pools, as well as multiple collections in a single user's pool.

Also add validation to prevent adding the same track/collection by the same user in the pool.

Originally created by @EddieTheCubeHead on GitHub (Apr 6, 2024). Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/193 Originally assigned to: @EddieTheCubeHead on GitHub. Backend and frontend should switch to communicating about pool members with pool member id instead of uri, as a single track can be a part of multiple users' pools, as well as multiple collections in a single user's pool. Also add validation to prevent adding the same track/collection by the same user in the pool.