Fix RestrictImplicitDependencyUsage to analyze per-module dependencies#3
Draft
Fix RestrictImplicitDependencyUsage to analyze per-module dependencies#3
Conversation
Co-authored-by: robertvansteen <14931924+robertvansteen@users.noreply.github.com>
Author
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Copilot
AI
changed the title
[WIP] Add coverage driver for code changes
Fix RestrictImplicitDependencyUsage to analyze per-module dependencies
Nov 10, 2025
Contributor
|
@copilot the tests are failing, can you fix them? |
Co-authored-by: robertvansteen <14931924+robertvansteen@users.noreply.github.com>
Co-authored-by: robertvansteen <14931924+robertvansteen@users.noreply.github.com>
Author
I've made several fixes in commits dd17c24 and 6bb2989 to address the test failures:
The latest workflow run (11) requires manual approval. Once approved, the tests should pass as the rule will now:
|
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.
The
RestrictImplicitDependencyUsagerule was readingcomposer.jsonfrom the project root for all files, causing it to use incorrect dependency constraints when analyzing files in subdirectories with their owncomposer.json.Changes
findModuleRoot()to locate the nearestcomposer.jsonby walking up from the analyzed filevendordirectory now fall back to using the project'svendor/composer/installed.jsonfor checking available packagesarray<string, T>caches keyed by module root path for:composerJsonCacheinstalledJsonCacheinstalledPackagesCacheallowedNamespacesCachecurrentModuleRootfrom$scope->getFile()before checking dependenciesThis fixes test cases that verify the rule correctly restricts dependencies in modules with different
composer.jsonfiles, particularly test modules that have their own dependency constraints but share the project's vendor directory.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.