Victorien Elvinger

By the way, I wonder if we should propose a common feature for both the summary and the [structured output proposals](https://github.com/biomejs/biome/discussions/128). Instead of providing a `--summary` flag, we could have...

> Should it be: > > useStringTrimStartEndMethod > useStringSliceMethod The unicorn rules don't retrieve type information. So, these rules apply to all methods named `trimLeft`, `trimRight`, `substring`, and `substr`. In...

> What do you think about --report instead? I think it is a better name. `--report` or `--reporter`? Not sure. Have you some use case for allowing several reporters at...

Anyway, I think it is a small thing. Choose the name you prefer and I think we are good for that.

> stderr is used for printing human readable messages, and stdout is used to printing machine readable messages. You are right. Even if `summary` is human-readable (at some extent), it...

Taking a look at the implementation, I wonder if we should also handle cases like: ```diff - const f = foo.substr; + const f = foo.slice; ```

Pretty nice :) Actually I was thinking of a general summary. However, I can see the interest for a file-based summary. Maybe we could add a general summary at the...

Once the conflicts resolved, I think we can merge this PR.

> Can you be more specific? ```shell ▶ ./packages/@biomejs/js-api/main.ts The file isn't formatted. Triggered lint rule Diagnostics lint/suspicious/noImplicitAnyLet 3 ▶ ./packages/@biomejs/js-api/main2.ts The file isn't formatted. Triggered lint rule Diagnostics lint/suspicious/noImplicitAnyLet...

You can disable the [strictCase](https://biomejs.dev/linter/rules/use-naming-convention/#strictcase) option? We are also working on implementing custom convention in #2770