Skip to content
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

use package:lints/recommended.yaml generally #180

Merged
merged 7 commits into from
Nov 6, 2023
Merged

Conversation

devoncarew
Copy link
Member

  • use package:lints/recommended.yaml generally
  • borrow a few lints from package:dart_flutter_team_lints to catch additional issues (moving to the whole set would let us have smaller analysis options configs here; we'd need to address a few more findings)

Note there there is one existing error - a doc reference - which I wasn't sure what to update it to.


  • I’ve reviewed the contributor guide and applied the relevant portions to this PR.
Contribution guidelines:

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

@devoncarew
Copy link
Member Author

Analyzing leak_tracker_flutter_testing...                       

   info • The referenced name isn't visible in scope • lib/src/test_widgets.dart:78:6 • comment_references

Screenshot 2023-11-03 at 2 09 33 PM

I'm not sure what that should be updated to -

@polina-c
Copy link
Contributor

polina-c commented Nov 3, 2023

Analyzing leak_tracker_flutter_testing...                       

   info • The referenced name isn't visible in scope • lib/src/test_widgets.dart:78:6 • comment_references
Screenshot 2023-11-03 at 2 09 33 PM I'm not sure what that should be updated to -

I will clean up this code very soon. This can be just deleted.

@@ -2,8 +2,6 @@
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

// ignore_for_file: avoid_print
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@polina-c - there are two print statements in this file; I suspect they're bugs (should be removed? the output routed to a file / to devtools?).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are not bugs. It is functionality, that will be used for tests. Tests are expected to output the information.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To stdout? What if users call that code? We'll produce random lines to their console.

Copy link
Contributor

@polina-c polina-c Nov 6, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, stdout. This output will happen if only user asked this to be outputed. Intentionally. The tests will output performance metrics. And, most likely it will be temporary just to create the baseline and will not be merged permanently.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, understood.

FYI that we are no longer reporting avoid_print (print uses) in this file in any case, as the linting is not based on flutter/lints.

@devoncarew devoncarew merged commit fbc2014 into main Nov 6, 2023
3 checks passed
@devoncarew devoncarew deleted the leak_tracker_analysis branch November 6, 2023 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants