-
Notifications
You must be signed in to change notification settings - Fork 1.4k
api cleanup in preperation for identity improvements #3214
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
Conversation
replaces some of the work done in #3152. this is the less risky subset of the changes, so we can create a separate PR for the more risky ones |
@swift-ci please smoke test |
@@ -95,7 +95,7 @@ public enum DependencyResolutionNode { | |||
// Don’t create a version lock for anything but a product. | |||
guard specificProduct != nil else { return nil } | |||
return PackageContainerConstraint( | |||
container: package, | |||
package: package, |
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.
Can we call this packageReference
?
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.
@neonichu we could, but in many other places in the code vase it is called "package". I actually have a commit with this change but its large if we want to be consistent. wdyt?
@@ -24,35 +24,35 @@ import TSCUtility | |||
/// should be used as-is. Infact, they might not even have a git repository. | |||
/// Examples: Root packages, local dependencies, edited packages. | |||
public final class LocalPackageContainer: PackageContainer { | |||
public let identifier: PackageReference | |||
public let package: PackageReference |
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.
Can we call this packageReference
?
motivation: infrastructure towards improve correctness by using identity more broadly throughout the code changes: * rename PackageReference::path to PackageReference::location * make PackageReference kinf explicitly set by the callsite with no default * rename PackageContainerConstraint::identifier to PackageContainerConstraint::package * rename PackageContainer::identifier to PackageContainer::package * adjust tests
ca6fab3
to
606a9e1
Compare
@swift-ci please smoke test |
@swift-ci please smoke test linux |
|
motivation: infrastructure towards improving package identity correctness
changes: