Expose archived cards via REST-API
Open
Nobody has claimed this yet.
backend
enhancement
feature parity
feature: api
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
The REST-API currently does not expose archived cards.
I propose to add a parameter ?archived=true for the stack endpoint which will only return the aechived cards of this stack.
The ETags with and without the parameter should be independent.
Contributor guide
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 at the REST API stack endpoint and trace the current card filtering and ETag behavior. Done means an archived=true request returns only archived cards, the default response remains unchanged, and the two response variants use independent ETags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100