-
Notifications
You must be signed in to change notification settings - Fork 23
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
Conversation
@@ -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 |
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.
@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?).
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.
They are not bugs. It is functionality, that will be used for tests. Tests are expected to output the information.
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.
To stdout? What if users call that code? We'll produce random lines to their console.
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.
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.
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.
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.
Note there there is one existing error - a doc reference - which I wasn't sure what to update it to.
Contribution guidelines:
dart format
.Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.