You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is consistent with other top level keys in that file: analyzer and linter. In those latter cases, those keys are also the name of the package. For complicated historical reasons, the formatter's package name is dart_style not formatter. It would probably be confusing if there was a package named formatter that had nothing to do with dart format or the formatter key in analysis_options.yaml.
Is it worth marking that name as reserved? As far as I can tell, there is no package on pub with that name today.
(Long-term, it might be nice to migrate dart_style to that name but that would be a lot of work for marginal benefit.)
The text was updated successfully, but these errors were encountered:
At long last, we're adding support to
dart format
for configuring page width at the project level. The configuration goes inanalysis_options.yaml
under aformatter
key:This is consistent with other top level keys in that file:
analyzer
andlinter
. In those latter cases, those keys are also the name of the package. For complicated historical reasons, the formatter's package name isdart_style
notformatter
. It would probably be confusing if there was a package namedformatter
that had nothing to do withdart format
or theformatter
key inanalysis_options.yaml
.Is it worth marking that name as reserved? As far as I can tell, there is no package on pub with that name today.
(Long-term, it might be nice to migrate
dart_style
to that name but that would be a lot of work for marginal benefit.)The text was updated successfully, but these errors were encountered: