dart_style VS prettier

> Oh I'm curious why you're rewriting it?

The primary driver is that we're moving to a fairly different formatting style: https://github.com/dart-lang/dart_style/issues/1253

The formatter works sort of like a compiler in that it parses the code, translates it to an internal representation, does optimization on that IR, and then outputs final code. The main difference is that the "final code" is also source code, and the "optimization" is line splitting.

The old IR grew organically over time and got increasingly difficult to work with. It baked certain formatting choices directly into the IR (mainly indentation) which line splitting then had no control over. For example, given a function call like:

    someLongFunctionName(some + long + argument + expression, [firstElement, anotherElement, aThirdElement]);

in your analysis_options.yaml. The formatter doesn't understand the new syntax yet, though.

Sorry, perhaps im not quite familiar with the GitHub issues you’re chatting about, but a quick search shows the Dart team actually made a very similar argument about laptops and diffs as the first reply in a thread about the 80 character max: https://github.com/dart-lang/dart_style/issues/833

Nope, but there is a proposal to set line length in pubspec.yaml: https://github.com/dart-lang/dart_style/issues/918

The standard Dart extension only supports formatting using the SDK-supplied formatter (dart_style) which (by design) is not configurable (although it can be turned on/off with the dart.enableSdkFormatter setting).

Flutter itself provides formatting choices, however, it only formats Dart files and it doesn’t re-order the code. Flutter formats the code based on these formatting rules.

There are some other possibilities - such as complex code being slow to format (for example I hit https://github.com/dart-lang/dart_style/issues/1022 and originally thought it was a repro for this issue), or that the server is busy doing its initial synchronous scan of the workspace, though those should be temporary and the format should eventually complete so it's probably not what most people are reporting here.

From my point of view, Prettier doesn't work well for styling with utility classes. For a discussion see Prettier#7863 or Prettier#5948.

Prettier: An opinionated code formatter that enforces a consistent code style.

Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency.

So anyways, I wanted to hook up Emacs with Astro support. For now, I've just been roughing it out there and running Prettier by itself and turning off save on format and auto-complete. It's been scary.

If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem.

prettier is used to format you text

No formatting inconsistencies: The committed code should follow the organization's code formatting standards(prettier or pretty-quick).

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.

GitHub | Website

Prettier: An opinionated code formatter that enforces a consistent code style.