MaibornWolff / MaibornWolff/codecharta
Visualization: Change specific folder names
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 529
- Forks
- 56
- Avg merge
- 7h 17m
- Merged PRs (30d)
- 34
Description
Feature request
Please provide the ability to change the name of folders.
Description
As a auditor, I want to change certain folder names, so that the screenshot is more self-explanatory.
I often have the situation where I want to give the root folder a special name to show what the map represents. Currently I create a box in PowerPoint and place it above the root folder. Here is an example from my recent article in JavaPro where I chronicle the evolution of the JDK (I also do this for audits but these picture are not public):
I use the delta-mode to compare two JDK states. So I overwrote the root node with "JDK x vs JDK y".
Another example is this one:
I had two files, one for JDK 10 and one for 24. I gave them a short name so the screen shot is better to read.
It is a bit annoying to do this with Powerpoint. Create the box, try and fail to make it match the perspective of the screenshot, put it above the root node or file node.
It would be great to have this in CodeCharta directly. I image another addition to the context menu. In addition to flatten and exclude, we can also change the display name of any selected node.
Acceptance criteria
- The node context menu in the map and in file tree has another entry to set the name of the node
- This setting is temporary
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 locating the node context menus in the map and file tree, then trace how selected-node display state is represented. Check how flatten and exclude actions are wired and verify that a temporary custom name appears in both views and is not persisted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100