-
Notifications
You must be signed in to change notification settings - Fork 1
Fix RestrictImplicitDependencyUsage to analyze per-module dependencies #3
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
base: fix-ci
Are you sure you want to change the base?
Conversation
Co-authored-by: robertvansteen <14931924+robertvansteen@users.noreply.github.com>
|
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 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>
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:
|
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.