-
Notifications
You must be signed in to change notification settings - Fork 28.9k
Add deprecation warning for "flutter create --ios-language" #155867
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -100,14 +100,15 @@ abstract class CreateBase extends FlutterCommand { | |
abbr: 'i', | ||
defaultsTo: 'swift', | ||
allowed: <String>['objc', 'swift'], | ||
help: 'The language to use for iOS-specific code, either Objective-C (legacy) or Swift (recommended).' | ||
help: '(deprecated) The language to use for iOS-specific code, either Swift (recommended) or Objective-C (legacy).', | ||
hide: !verboseHelp, | ||
); | ||
argParser.addOption( | ||
'android-language', | ||
abbr: 'a', | ||
defaultsTo: 'kotlin', | ||
allowed: <String>['java', 'kotlin'], | ||
help: 'The language to use for Android-specific code, either Java (legacy) or Kotlin (recommended).', | ||
help: 'The language to use for Android-specific code, either Kotlin (recommended) or Java (legacy).', | ||
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. I don't know enough abt this area but does this section need 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.
|
||
); | ||
argParser.addFlag( | ||
'skip-name-checks', | ||
|
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.
Do we want this call to action for all cases, or just plugins? I was envisioning just the latter, since the usage is higher there.
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.
I figured I would do it for all in case there's some super compelling reason for the app template as well that I haven't thought of. This should be a rare warning.
I did remove the module check since no one should be using the flag for that template anyway, may as well warn them it's being removed if they are using it for some weird reason.