solution for too many lists
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
What to do when you have more than 100 lists?
a) delete them? no I need to keep a written record of what I have done.
b) export them? yes, that way I can delete them on the server.
c) hide them? yes, that's the best solution
Can you suggest a solution please?
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 reviewing the screenshot and the issue discussion to understand the current limit and the proposed export or hiding behavior. Locate the list-management entry point in the Deck client, then define the expected behavior for more than 100 lists and verify that existing records remain accessible or exportable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100