MaibornWolff / MaibornWolff/codecharta

Exclude/flattened not obvious in file node explorer

Open
#4,136 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
529
Forks
56
Avg merge
7h 17m
Merged PRs (30d)
34

Description

# Feature request

Currently the behavior of exclude/flattened files in the node explorer is inconsistent and confusing to novice users. This was a user feedback a while back. Can we make it more obvious and consistent?

## Description

As a novice user, I want consistent and obvious behavior in the node explorer, so that I can understand what is going on.

## Acceptance criteria
- When I flatten something, the node explorer displays an explaining tooltip why it's gray (currently nothing) and displays the same flatten icon that I used to flatten it in the context menu. The icon is not behind the three dots burger menu as it is currently.

Current:
Image

- When I exclude something, the node explorer displays an explaining tooltip why it's gray (currently shows "no area metrics" which is wrong) and displays the same exclude icon that I used to exclude it in the context menu (currently shows not .

- When a file does not have an area metric we can perhaps improve the tooltip to say: "Does not have area metric."
- Right-clicking a file that does not have an area metrics opens a small modal (currently nothing happens, which is confusing), same style as the context menu. This modal says something like: "The file/folder cannot be visualized in the map because it does not have the selected area metric. Either select a different area metric or see if another analyzer can generate the metric for you."

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the node explorer and its context-menu handling, tracing the existing flatten, exclude, and missing-area-metric states. Compare the displayed icons, gray-state tooltips, and right-click behavior with the acceptance criteria; done means each state explains itself and uses the requested icon or modal.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
design, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.