Bob Nystrom

> Please allow line length setting to be set in pubspec as not having this causes problems for anyone no wanting to use default 80 chars. dartfmt does not have...

Copying my comment from [here](https://github.com/dart-lang/pub-dev/issues/3956#issuecomment-1010553599): Dart format does not have any notion of "project" or "package" and doesn't know where to look for any sort of global or package-level configuration...

> This debate is already being had, This is true *for some teams*, but not all. If we add support for configuring it the formatter, than we will expand the...

> We should either remove the ability to format at custom line lengths entirely, or complete the implementation and allow it to be set at the project level Many many...

> The "But googlers don't need it" argument is not as good as you think - are you going to tell us to write shorter function and variable names to...

> If you say " isn't recommended" then why is it an option to start with? Many of the lint rules exist to help users migrate from previous versions of...

Yeah, I agree the examples in this issues all look pretty bad. They're a result of some limitations in how the formatter's internal representation currently works. (The short summary is...

OK, now that the [forthcoming](https://github.com/dart-lang/dart_style/issues/1403) [tall style](https://github.com/dart-lang/dart_style/issues/1253) is further along, I ran all of these examples through it. Here's the output: ```dart void main() async { (await { 'asdf': 'fdsa',...

I agree, the output is not great here. Output like this is one of the reasons why we're rewriting the formatter and moving to a new style (#1253). With the...

This is working as *intended* but I'm not sure at all if it's working as *desired*. When an argument list has a trailing comma, the formatter currently treats it exactly...