Micha Reiser

Not there yet but we'll have to document the two new commands * #3410 * #3411

* #3442

We should update the README.md of the Rome VS Code extension to explain how to make Rome the default formatter and add a link to the website's getting started guide.

We need to remove all references to `rome@next`

Closing in favour of https://github.com/rome/tools/issues/3575

> ### Analyzer Benchmark Results > ``` > group main pr > ----- ---- -- > analyzer/css.js 1.00 2.3±0.01ms 5.1 MB/sec 1.01 2.3±0.01ms 5.0 MB/sec > analyzer/index.js 1.00 6.5±0.01ms 5.0...

@ematipico is this something you could help me with? If I remember correctly then it was you who implemented our current string cleaning.

> I try to take this issue 🚀 Awesome. I assigned the task to you. You can find the current logic [here](https://github.com/rome/tools/blob/5e45610dc563a64808fdbf127334226a3141e271/crates/rome_js_formatter/src/utils/string_utils.rs#L407) (it's a bit involved)

> > My main concern is around naming where there is a mix between "Settings" and configuration > > I can see the confusion that settings and configuration can cause,...

@xunilrj would this be a formatter improvement you're interested in tackling? I know you're good at high performance string manipulation :)