Feature Request: Add IDs Endpoint
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Feature Request: Add ID's Endpoint
Currently it's not possible to fetch only the Ids of the followers/favorites etc. That makes it really ressource intensive to figure out, which tracks the user has a relationship since we need to page through a lot of data. (the details of the tracks or users are not needed here).
API-v2 is providing this functionality. It would be to see this in the API.
Endpoint(s):
GET /users/{id}/followings/idsGET /users/{id}/followers/idsGET /users/{id}/favorites/idsGET /users/{id}/reposts/ids
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
Review the API-v2 behavior referenced in the issue and compare it with the existing Public API relationship endpoints. Define the response and behavior for the four listed ID paths, then add coverage for each endpoint. Done means callers can fetch only followings, followers, favorites, and repost IDs without paging through full resource details.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100