eclipse-cdt-cloud / eclipse-cdt-cloud/vscode-trace-extension

[maintainability] Cycles found in extension's code

Open
#207 1 comment 0 reactions 0 assignees View on GitHub
tech debt
Dominant language
TypeScript
Stars
11
Forks
33
Avg merge
2d 16h
Merged PRs (30d)
1

Description

After updating to a more recent version of `Eslint`, the linter started to report an issue with `ProgressMessages` in `vscode-trace-extension/src/trace-explorer/trace-tree.ts` having already been defined. After scratching my head for a while, I thought it could be a "cycle" issue. That turned-out to apparently be correct: see yellow lines in this graph, generated using "dependency-cruiser" \[1\]. The worst of it seems centered around `extension.ts`

Dependency graph (look at the yellow lines):

![dependency-graph-only-extension](https://github.com/eclipse-cdt-cloud/vscode-trace-extension/assets/25749063/252b1ef4-f6c8-4b08-9e17-ddaa7dd76902)

For info about the configuration I used and how to run `dependency-cruiser`, see this [commit on my fork](https://github.com/marcdumais-work/vscode-trace-extension/commit/e126c8751bbce622381f70a42ab69d5ca4bd1117)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.