-
Notifications
You must be signed in to change notification settings - Fork 147
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
Support different line lengths #3041
Comments
I don't think we can or should do anything in the short term. But this is solid input for the debate about what lints we should use to score packages. |
I think this is not something hard to complete, the simplest way is just ignore length check, I think it should be done as soon as possible. |
Allow us to have some max-lines attribute in the pubspec.yaml... fetch that on your score calculator. |
It would be nice if you could support different line lengths, e.g.
-l 120
parameter topana
. While 80 is a recommendeddartfmt
default, some projects don't want to use that and instead opt for a different number.Currently, it's reported as a "Health suggestion" on the package analysis tab:
Health suggestions
Format
path/to/file.dart
.Run
dartfmt
to formatpath/to/file.dart
.I don't think it's a project health issue as long as the whole project is consistent with the formatting, albeit with a different line length than the default 80. While I understand these suggestions have no negative impact on the score I'd still prefer them not to show up on the page at all.
Is there something that can be done about it? Maybe some simple configuration file or a config in the pub.dev admin section?
The text was updated successfully, but these errors were encountered: