[Dependency Scanning] Pull required dependencies from the adjacent binary module for direct '@testable' interface dependencies

They may be a super-set of the ones that appear in the textual interface - e.g. 'internal' imports will be contained in the adjacent binary module, but not the textual interface
This commit is contained in:
Artem Chikin
2023-04-17 16:34:38 -07:00
parent 6fcd8be072
commit 4e520e44a2
3 changed files with 58 additions and 12 deletions

View File

@@ -420,7 +420,7 @@ SerializedModuleLoaderBase::getModuleImportsOfModule(
/*debuggerMode*/ false,
/*isPartialModule*/ false, packageName,
loadedModuleFile->isTestable());
if (dependencyTransitiveBehavior != transitiveBehavior)
if (dependencyTransitiveBehavior > transitiveBehavior)
continue;
// Find the top-level module name.