feat: add Angular framework support for understand analysis#543
Open
BrahmendraBachi wants to merge 1 commit into
Open
feat: add Angular framework support for understand analysis#543BrahmendraBachi wants to merge 1 commit into
BrahmendraBachi wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feat: add Angular framework support for /understand analysis
Summary
Adds Angular as a built-in framework in the analysis pipeline so
/understandcan auto-detect Angular projects (@angular/coreinpackage.json) and inject an Angular-specific prompt addendum into file-analyzer and architecture-analyzer. The addendum documents canonical file roles (components, services, guards,*.import.const.ts, etc.), edge patterns (DI, routing, standalone composition), and layer assignments—improving knowledge-graph quality for Angular codebases.Linked issue(s)
How I tested this
pnpm lintpnpm --filter @understand-anything/core test—framework-registry.test.tsupdated for 11 built-in frameworkspnpm test/understandon an Angular project with@angular/corein dependencies; confirmedangularappears in scan metadata and the graph includes component/DI/routing edges (e.g.depends_onfrom components to services,configuresfrom route files)Versioning