-
Notifications
You must be signed in to change notification settings - Fork 8
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
fix: improve handling of pvc path flag #129
Conversation
@W-11903179@
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.
Looks to me like we can remove a bunch of code in package beta version create command and rely on the library.
@@ -221,4 +209,24 @@ export class PackageVersionCreateCommand extends SfdxCommand { | |||
} | |||
return result; | |||
} | |||
|
|||
private resolvePackageIdFromFlags(): string { |
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.
PackageVersion.create()
handles all of this already right? That's what I see when looking at library code for packageVersionCreate.packageVersionCreate()
.
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.
It should (there is a bug in that code), but I really do not like passing a path as an id or alias. To me it is just making the determination of which package much more difficult.
What does this PR do?
Improves handling of the path flag for package version create
What issues does this PR fix or reference?
@W-11903179@ GH issue