-
Notifications
You must be signed in to change notification settings - Fork 9.8k
[all] Switch to pedantic analysis rules #2300
Conversation
Switches our out of date fork of Flutter's analysis rules to the pedantic package. In order to make this an easy change to initially land and then incrementally enable, any existing non-trivial lints have just been ignored within their respective packages instead of being fixed. Also adds a global lint for missing public DartDocs. Like the pedantic lints, this being ignored in packages that are already failing it.
// This is a temporary ignore to allow us to land a new set of linter rules in a | ||
// series of manageable patches instead of one gigantic PR. It disables some of | ||
// the new lints that are already failing on this plugin, for this plugin. It | ||
// should be deleted and the failing lints addressed as soon as possible. | ||
// ignore_for_file: public_member_api_docs |
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.
Originally I tried putting in an analysis_options.yaml
for this plugin like everywhere else, but for some reason this particular plugin was having issues importing the pedantic
package transitively when running pub global tuneup
. No idea why as the package was showing as included in the pubspec.lock
and nothing looked different from any of the other packages. Seems like some kind of bug to me in pub or the linter to me. I'm just working around it by putting the ignores in the source code directly instead. It's not ideal, but it shouldn't matter since in the long term this should be fixed anyway.
@@ -10,6 +10,6 @@ Future<void> main() async { | |||
final FlutterDriver driver = await FlutterDriver.connect(); | |||
final String result = | |||
await driver.requestData(null, timeout: const Duration(minutes: 1)); | |||
driver.close(); | |||
await driver.close(); |
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.
Wow, this is a good catch.
Switches our out of date fork of Flutter's analysis rules to the pedantic package. In order to make this an easy change to initially land and then incrementally enable, any existing non-trivial lints have just been ignored within their respective packages instead of being fixed. Also adds a global lint for missing public DartDocs. Like the pedantic lints, this is ignored in packages that are already failing it.
Switches our out of date fork of Flutter's analysis rules to the pedantic package. In order to make this an easy change to initially land and then incrementally enable, any existing failures have just been ignored within their respective packages instead of being fixed. Also adds a global lint for missing public DartDocs. Like the pedantic lints, this is ignored in packages that are already failing it. This is a mirror of a similar change to flutter/plugins, flutter#2300.
Switches our out of date fork of Flutter's analysis rules to the pedantic package. In order to make this an easy change to initially land and then incrementally enable, any existing non-trivial lints have just been ignored within their respective packages instead of being fixed. Also adds a global lint for missing public DartDocs. Like the pedantic lints, this is ignored in packages that are already failing it.
Description
Switches our out of date fork of Flutter's analysis rules to the
pedantic package. In order to make this an easy change to initially land
and then incrementally enable, any existing non-trivial lints have just
been ignored within their respective packages instead of being fixed.
Also adds a global lint for missing public DartDocs. Like the pedantic
lints, this is ignored in packages that are already failing it.
Related Issues
flutter/flutter#45440
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
). This will ensure a smooth and quick review process.///
).flutter analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?