Plugin import scanner isn't passing in the library directory, making canImport
not work
#6323
+15
−4
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 Workspace type has a facility for scanning package plugins for imports. But since it's not passing in the actual plugin directory provided by the caller (whether it's SwiftPM or Xcode), any modules provided by an IDE aren't picked up if they are guarded by
#if canImport()
. This includesXcodeProjectPlugin
, which is one of the additional plugin modules provided by Xcode. The same would be true for other IDEs.Changes:
Workspace.loadPluginImports
now also passes the path of the plugin directory to the import scanningtestScanImportsInPluginTargets
unit test to check for this caserdar://106387043