Nice, flattered that you use my plugin now at openstreetmap ;) If anything is
not working, just [open an
issue](https://github.com/Splines/eslint-plugin-erb). And feel free to leave a
GitHub star should you like it 😊
--
Reply to this email directly or view it on GitHub:
https://github.com/open
Just to add my two cents: it's very common to have a `.vscode` in your repo if
many devs use VSCode. If you don't want to see the folder locally, you can even
add this to the `.vscode/settings.json`:
```ts
"files.exclude": {
".vscode": true,
}
```
There are so many great settings you can spec
If you introduce linting here you might also be interested in:
- How we use ESLint on GitHub Actions via [this
file](https://github.com/MaMpf-HD/mampf/blob/23aae01471c4361b85e86df06e349cd8acfb735c/.github/workflows/linter.yml#L39-L75)
to lint only the changes inside changed `.js` and `.js.erb` f
> Up until now, whenever I was writing JavaScript, I struggled to get ESLint to
> work as seamlessly as Prettier
@kcne Feel free to use a configuration like the one [I use
here](https://github.com/Manim-Notebook/manim-notebook/blob/68874a7e30489d8774ffc53ddfd96cbc7d885ba6/.vscode/settings.json#L
> Most stylistic rules are now removed from eslint because most use a formatter
> like prettier.io
@HolgerJeromin Formatting rules have indeed been
[deprecated](https://github.com/eslint/eslint/issues/17522) in the _core_ of
ESLint. But mainly because of ongoing maintenance cost. Luckily, antfu
