Expose board settings per user 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
We should synchronize
- compact mode
- show archived cards
- and (maybe in a second step because of its complexity) the current filter information (due date, assignees, tags)
Therefore it has to be exposed via the API. Since this is a per user / per board setting, we have to think about how to implement this in detail, but i am sure this will greatly enhance the UX.
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 by locating Deck's existing REST API endpoints and the code that stores compact mode, archived-card visibility, and per-board user settings. Define how the first two settings should be exposed and synchronized; treat due-date, assignee, and tag filters as a separate follow-up unless their scope can be resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100