Tracks played via a stream retrieved from the API do not appear in the authenticated user's listening history.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Title: Tracks played via a stream retrieved from the API do not appear in the authenticated user's listening history.
Issue found of: March 24th, 2022
Endpoint(s):
GET /tracks/{id}/streams
Scope(s):
- None (application is not using authentication i.e., implicit flow)
Steps to reproduce:
curl --request GET \
--url 'https://api.soundcloud.com/tracks/308946187/streams" -H "accept: application/json; charset=utf-8'
Expected behaviour:
It would be great if Tracks played via a stream retrieved from the API appeared in the authenticated user's listening history.
Actual behaviour:
Tracks played via a stream retrieved from the API do not appear in the authenticated user's listening history.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with GET /tracks/{id}/streams and the issue's curl reproduction, then review how implicit-flow requests and listening-history events are handled. Done means confirming that tracks played through an API-retrieved stream appear in the authenticated user's listening history, with coverage for the reported request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100