commit | 7f6b170625ffa3395734d57c74264130c5de9b71 | [log] [tgz] |
---|---|---|
author | Bob Nystrom <rnystrom@google.com> | Thu Mar 28 11:48:49 2024 -0700 |
committer | GitHub <noreply@github.com> | Thu Mar 28 11:48:49 2024 -0700 |
tree | 910786ef1698018efbdd79421e916a4f57a28e43 | |
parent | 2278fcd9eb1d9417c9e674a560410c244a9d8b76 [diff] |
Don't indent split binary operands in an assignment-like context. (#1431) Don't indent split binary operands in an assignment-like context. Binary operators indent their subsequent operands in most places: ```dart function( operand1 + operand2 + operand3, ); ``` But it's gratuitous on contexts where a split between the operands will also lead to a split before the operand. In that case, it looks nicer to align the operands: ```dart variable = operand1 + operand2 + operand3; ``` The places where this can occur are "assignment-like": the right-hand side of `=`, `:`, or `=>`. This is another example where the relationship between a parent and child AST node affects how they are formatted. We don't have a great systematic way of modeling those relationships in the codebase right now. Sometimes, we have the code building the parent Piece peek at the child's AST node type and do something different with the child based on that. Sometimes, the child calls `.parent` on itself and peeks at the parent type. We don't generally look at the type of the Piece of the child because we don't consider that to be reliably encoding what kind of original syntax it came from (though we could). This takes yet another approach where we allow a parent AST node to pass in a "context" when visiting one of its children. A child can then look at that context to tweak its formatting. I'm not sure if I love the approach, but I thought I'd give it a try and see what you think.
The dart_style package defines an automatic, opinionated formatter for Dart code. It replaces the whitespace in your program with what it deems to be the best formatting for it. Resulting code should follow the Dart style guide but, moreso, should look nice to most human readers, most of the time.
The formatter handles indentation, inline whitespace, and (by far the most difficult) intelligent line wrapping. It has no problems with nested collections, function expressions, long argument lists, or otherwise tricky code.
The formatter turns code like this:
// BEFORE formatting if (tag=='style'||tag=='script'&&(type==null||type == TYPE_JS ||type==TYPE_DART)|| tag=='link'&&(rel=='stylesheet'||rel=='import')) {}
into:
// AFTER formatting if (tag == 'style' || tag == 'script' && (type == null || type == TYPE_JS || type == TYPE_DART) || tag == 'link' && (rel == 'stylesheet' || rel == 'import')) {}
The formatter will never break your code—you can safely invoke it automatically from build and presubmit scripts.
The formatter can also apply non-whitespace changes to make your code consistently idiomatic. You must opt into these by passing either --fix
which applies all style fixes, or any of the --fix-
-prefixed flags to apply specific fixes.
For example, running with --fix-named-default-separator
changes this:
greet(String name, {String title: "Captain"}) { print("Greetings, $title $name!"); }
into:
greet(String name, {String title = "Captain"}) { print("Greetings, $title $name!"); }
The formatter is part of the unified dart
developer tool included in the Dart SDK, so most users get it directly from there. That has the latest version of the formatter that was available when the SDK was released.
IDEs and editors that support Dart usually provide easy ways to run the formatter. For example, in WebStorm you can right-click a .dart file and then choose Reformat with Dart Style.
Here's a simple example of using the formatter on the command line:
$ dart format test.dart
This command formats the test.dart
file and writes the result to the file.
dart format
takes a list of paths, which can point to directories or files. If the path is a directory, it processes every .dart
file in that directory or any of its subdirectories.
By default, it formats each file and write the formatting changes to the files. If you pass --output show
, it prints the formatted code to stdout.
You may pass a -l
option to control the width of the page that it wraps lines to fit within, but you're strongly encouraged to keep the default line length of 80 columns.
If you want to use the formatter in something like a presubmit script or commit hook, you can pass flags to omit writing formatting changes to disk and to update the exit code to indicate success/failure:
$ dart format --output=none --set-exit-if-changed .
If you need to run a different version of the formatter, you can globally activate the package from the dart_style package on pub.dev:
$ pub global activate dart_style $ pub global run dart_style:format ...
The package also exposes a single dart_style library containing a programmatic API for formatting code. Simple usage looks like this:
import 'package:dart_style/dart_style.dart'; main() { final formatter = DartFormatter(); try { print(formatter.format(""" library an_entire_compilation_unit; class SomeClass {} """)); print(formatter.formatStatement("aSingle(statement);")); } on FormatterException catch (ex) { print(ex); } }
Before sending an email, see if you are asking a frequently asked question.
Before filing a bug, or if you want to understand how work on the formatter is managed, see how we track issues.