-
Notifications
You must be signed in to change notification settings - Fork 1
Support .NET dependencies #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
fefa5f6 to
b69c0dc
Compare
b69c0dc to
7f40287
Compare
0cb58d3 to
fc8ab21
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds support for .NET projects by introducing a new dotnet dependency manager, updating rules, tests, and documentation to detect Blazor and ASP.NET Core frameworks.
- Implemented
dotnetManagerto parse.csprojandpackages.lock.jsonfiles - Registered the new
.NETmanager and added unit tests for various version scenarios - Extended rule configurations and test data to detect Blazor WebAssembly, Blazor Server, and ASP.NET Core
Reviewed Changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| pkg/dep/dotnet.go | New .NET manager implementation |
| pkg/dep/dotnet_test.go | Tests covering .NET manager behavior |
| pkg/dep/dep.go | Added dotnet to manager types and registration |
| pkg/rules/testdata/mock-blazor/ | Test assets for Blazor project (.csproj and packages.lock.json) |
| pkg/rules/analyze_testfs_test.go | Extended test cases to include Blazor frameworks and msbuild |
| docs/functions.md | Documented depExists/depVersion for dotnet |
| config/frameworks.yml | Added rules for Blazor WebAssembly, Blazor Server, and ASP.NET Core |
| expr.cache | Updated expression cache to include dotnet functions |
Comments suppressed due to low confidence (3)
config/frameworks.yml:614
- The group order for
blazor-wasmis[dotnet, blazor], but the test expects[]string{"blazor", "dotnet"}. Swap the order to match the test.
group: [dotnet, blazor]
pkg/rules/analyze_testfs_test.go:126
- Add a test case for the
blazor-serverrule inTestAnalyze_TestFS_ActualRulesto cover server-side Blazor detection.
{Ruleset: "frameworks", Path: "blazor-app", Result: "blazor-wasm", Rules: []string{"blazor-wasm"},
docs/functions.md:14
- [nitpick] Use proper nested list syntax in Markdown (e.g., indent with two spaces) so that parameter bullets under
depExistsanddepVersionrender correctly.
- `fs`: The filesystem, representing each directory
No description provided.