[RFC] Naming the Graph Tabs #8
fosfor15
started this conversation in
Ideas & RFCs
Replies: 2 comments
-
|
I prefer Architecture for Tab 1 and View Tree for Tab 2. These names feel the most intuitive and clean for a user interface |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi! I vote for the "Architecture", "View Tree" and "DI Hierarchy". Thank you for the well-documented and supported project! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone! 👋
As GraphLens continues to expand its visualization capabilities (including future features like the DI Graph), the extension panel needs a consistent and clear naming system for its tabs. Before making a final decision, this RFC is meant to share the current concepts and gather community feedback. Based on this discussion, a final Poll will be created later.
The Naming Concept
Graph vs Hierarchy: To make the tab names technically accurate, the proposed naming system is based on internal topology:
Additionally, these proposals are inspired and justified by Angular documentation.
Here are the tabs and the naming options under consideration:
Tab 1: The Application Architecture (Modules & Standalone)
This tab shows the structural building blocks and architectural relationships of the app's core entities: NgModules, Standalone components, and their imports.
Options:
Architecture,Structure Hierarchy,Imports HierarchyTab 2: Visual Entities (UI & Templates)
Currently, this tab visualizes the "Component tree": Components, Directives, and their relationships. The goal is to rename this tab to reflect its different entity types. Since components can technically have circular or even recursive relationships in their templates, this structure can behave as a graph, but it is ultimately rendered and commonly known as a tree. The word
Viewis taken from Angular documentation, where it refers to a fundamental UI block.Options:
View Tree,UI Tree,View Graph,UI GraphTab 3: Dependency Injection (Upcoming in Q2-Q3)
This future tab will visualize the DI system: Injectors, Providers, Tokens, and DI-content. Since Angular's DI resolution bubbles up strictly in one direction and completely forbids circular dependencies, it is a perfect hierarchy.
Options:
DI Hierarchy,DI SystemWhat are your thoughts and ideas?
Which naming combination feels the most natural and professional from an Angular developer's perspective? Are there any other suggestions?
Let's discuss it in the comments below! 👇
Beta Was this translation helpful? Give feedback.
All reactions