Closed munificent closed 2 months ago
This actually shouldn't affect the SDK at all. The SDK is already using newer CLI and the newer DartFormatCommand
class. This is just removing the old stuff that you can only access directly through the dart_style package's own CLI.
Before the
dart format
command was added to the core Dart SDK, users accessed the formatter by running a separatedartfmt
executable that was included with the Dart SDK. That executable had a different CLI interface. For example, you had to pass-w
to get it to overwrite files and if you passed no arguments at all, it silently sat there waiting for input on stdin. When we addeddart format
, we took that opportunity to revamp the CLI options.However, the dart_style package still exposed an executable with the old CLI. If you ran
dart pub global activate dart_style
, this would give you adartfmt
(anddartformat
) executable with the old CLI options. Now that almost everyone is usingdart format
, we have removed the old CLI and the old package executables.You can still run the formatter on the CLI through the package (for example, if you want to use a particular version of dart_style instead of the one bundled with your Dart SDK). But it now uses the exact same CLI options and arguments as the
dart format
command. You can invoke it withdart run dart_style:format <args...>
.