API does not include a way of filtering Blocked content when using /resolve.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Title: API does not include a way of filtering Blocked content when using /resolve.
Issue found of: March 24th, 2022
Endpoint(s):
GET /resolver
Scope(s):
- None (application is not using authentication i.e., implicit flow)
Steps to reproduce:
curl --request GET \
--url 'https://api.soundcloud.com/resolve?url=https%3A%2F%2Fsoundcloud.com%2Fuser-434241656'
Expected behaviour:
API does not include a way of filtering Blocked content when using /resolve.
Actual behaviour:
Blocked content is returned in the results.
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 documented GET /resolve endpoint and reproduce the supplied curl request against the referenced SoundCloud URL. Determine how blocked content should be filtered in the response; done means the endpoint offers and correctly applies that filtering behavior, with the result verified against blocked content.
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
- Mostly clear
- Newbie friendliness
- 35/100