-
Notifications
You must be signed in to change notification settings - Fork 19
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: more flag conflicts #861
Conversation
@@ -65,11 +66,6 @@ export class Retrieve extends SourceCommand { | |||
summary: messages.getMessage('flags.retrievetargetdir.summary'), | |||
exclusive: ['packagenames', 'sourcepath'], | |||
}), | |||
apiversion: Flags.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.
api-version
was on the command, but another api-version
was the one actually being used in the code below. I think this was just to get a char alias the hard way, but that meant api-version
was being ignored.
public static readonly state = 'deprecated'; | ||
public static readonly deprecationOptions = { | ||
to: replacement, | ||
message: messages.getMessage('deprecation', [replacement]), | ||
}; | ||
public static readonly flags = { | ||
'api-version': orgApiVersionFlagWithDeprecations, | ||
// I have no idea why 'a' isn't matching the type AlphabetLowercase automatically | ||
'api-version': { ...orgApiVersionFlagWithDeprecations, char: 'a' as AlphabetLowercase }, |
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.
lol
created via github action [skip-validate-pr]