Feat: Improve column type dropdown with sorting & visibility
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Is your feature request related to a problem? Please describe.
We a re running a long lasting Tables app, where users are placing registration requests for certain events.
They register for a specific event by handling a dropdown, which holds the specific event entries.
They are manually sorted by date, which means that we had to create them in order, since other means of sorting entries is not possible. We now face the problem, that an additional event in between existing ones would need to be placed. But that's not possible and we have to add it to the bottom for now, which is not really great.
The dropdown should also no longer show past events to users, while existing records with past entries should still remain visible for history reasons.
Describe the solution you'd like
-
Allow to drag & drop dropdown entries up and down the list of entries
-
Add per dropdown entry a checkbox for "visibility", which controls, if that entry is shown to users in the dropdow entry list. Since that affects only newly added records, existing records must still show those entries.
Describe alternatives you've considered
Probably some "patch" with CSS could help for the time being, but yeah, it's just a poor mans patch
Additional context
No response
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 the column type dropdown implementation and the code that persists dropdown entries. Trace how new selections and existing records are handled, then define the drag-and-drop ordering and visibility behavior, including hidden past entries remaining visible in existing records. Done means entries can be reordered, visibility can be changed per entry, and both new and historical records follow the requested rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- database, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100