How can we tell whether tracks are ready to embed with the new API?
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Title: How can we tell whether tracks are ready to embed with the new API
Issue found of: May 11th, 2021
Endpoint(s):
POST /tracks/{track_id}
Steps to reproduce:
Please see https://github.com/soundcloud/api/issues/67
Expected behaviour:
Please see https://github.com/soundcloud/api/issues/67
Actual behaviour:
Please see https://github.com/soundcloud/api/issues/67
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 the POST /tracks/{track_id} endpoint and read the discussion in issue 67, which this issue references for reproduction and expected behavior. Determine from that discussion what readiness signal or API behavior is being requested; the issue is complete only when the expected way to identify tracks ready for embedding is defined and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100