Support for key_signature and bpm
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Hey team!
Does the API support the key_signature and bpm fields in the /tracks endpoint? I can see it as part of the response structure but they contain null values when I query for any track. Thanks!
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 by reviewing the /tracks endpoint documentation and reproducing a track query that returns null for key_signature and bpm. Determine whether these fields are supported and whether the response matches the documented behavior; the issue is complete when the behavior is corrected or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100