-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[SR-14782] swift package describe
is omitting product dependencies from per-target output
#3556
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
Merged
abertelrud
merged 1 commit into
swiftlang:main
from
abertelrud:eng/product-dependencies-are-missing-from-package-describe
Jun 21, 2021
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -254,6 +254,21 @@ final class PackageToolTests: XCTestCase { | |
XCTAssert(textChunk6.contains("Path: Sources/CExec"), textChunk6) | ||
XCTAssert(textChunk6.contains("Sources:\n main.c"), textChunk6) | ||
} | ||
|
||
fixture(name: "DependencyResolution/External/Simple/Bar") { prefix in | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This uses an existing test fixture so we don't need to add more of them. |
||
// Generate the JSON description. | ||
let jsonResult = try SwiftPMProduct.SwiftPackage.executeProcess(["describe", "--type=json"], packagePath: prefix) | ||
let jsonOutput = try jsonResult.utf8Output() | ||
let json = try JSON(bytes: ByteString(encodingAsUTF8: jsonOutput)) | ||
|
||
// Check that product dependencies and memberships are as expected. | ||
XCTAssertEqual(json["name"]?.string, "Bar") | ||
let jsonTarget = try XCTUnwrap(json["targets"]?.array?[0]) | ||
XCTAssertEqual(jsonTarget["product_memberships"]?.array?[0].stringValue, "Bar") | ||
XCTAssertEqual(jsonTarget["product_dependencies"]?.array?[0].stringValue, "Foo") | ||
XCTAssertNil(jsonTarget["target_dependencies"]) | ||
} | ||
|
||
} | ||
|
||
func testDescribePackageUsingPlugins() throws { | ||
|
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.
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.
cc @yim-lee for potential impact on collection generator
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.
In theory this should have no impact since it's additive, but that's a good point. I guess this would have the effect of omitting the
target_dependencies
empty array for a target that had only product dependencies, in addition to adding theproduct_dependencies
array. I don't know if product dependencies is something that you might want to start including in the collections at some point — I don't think that's in the data structures now (are target dependencies there now?).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.
👍 thanks.
The generator is not using
describe
yet (but will), so this change has no impact. I don't think we will include*_dependencies
in the package collection data, but IIRC the intention is that it will help determine which targets to include (i.e., only targets included in a product).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.
Sounds good. That's in the separate
product_memberships
array, and unaffected by this.