MaibornWolff / MaibornWolff/codecharta
Improve unintuitive behaviour of deleting maps
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 529
- Forks
- 56
- Avg merge
- 7h 17m
- Merged PRs (30d)
- 34
Description
Feature request
When i click on the button to delete the map thats currently selected, it unselects this map, disabling the apply button. As the user clicked to delete the map, not to unselect it, they are likely unaware that currently no map is selected and wonder why they cannot apply the delete. My suggestion is to keep the apply button active in this case (or in general when no map is selected) and to show the top most map if none were selected
Description
As a user, I want be able to delete the current map without having to manually select another map.
Acceptance criteria
Assumptions & Exclusions
Development notes (optional Task Breakdown)
Open questions
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
Start by tracing the frontend flow for deleting the currently selected map and how selection controls the Apply button. Confirm the behavior when the selected map is deleted and when no map is selected; done means the user can delete the current map without manually selecting another and the topmost map is shown when nothing is selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100