Martin Törnqvist

It seems like `prettier-plugin-svelte` isn't compatible with `eslint-plugin-svelte3` via `eslint-plugin-prettier`, however meanwhile we can still extend `eslint-config-prettier` and call prettier _separately_ from eslint i.e. directly from the editor. For those...

Did some debugging, seems like `eslint-plugin-svelte3` only extracts JS from the `` part and returns this (through `eslint-plugin-prettier`) for prettier to parse, meanwhile `prettier-plugin-svelte` expects a whole .svelte file to...

@SteveALee Yeah the answer to [sveltejs/svelte#3550](https://github.com/sveltejs/svelte/issues/3550) is what's making me confused. It would seem like exactly the right place to resolve the problem. Maybe we can try to get it...

EDIT: In the [TypeScript roadmap](https://github.com/sveltejs/svelte/issues/4518) they already mention separation of the Svelte core from tooling and taking inspiration from Vue, and UnwrittenFun seems involved in this. So focusing on `eslint-plugin-prettier`...

It seems as if this has already been merged elsewhere, should it be closed?

@fforres Oh no I'm sorry, I must be sleep deprived. I thought I saw the exact same lines by the same author on the main branch, and somehow forgot that...

Right, those rules don't seem that great, I'll probably remove both. But they revealed that there are unknown & unexplained interactions in my linting which is pretty uncomfortable. :-) Sorry...

@bradzacher I peeled off as much as I could: [toerndev/reproduce-eslint-issue](https://github.com/toerndev/reproduce-eslint-issue)

So `pattern` uses the minimatch format, if we can match everything we want in a group with one pattern, there won't be any newlines. `foo|bar` or `(foo|bar)` don't match foo...

@lydell FWIW I think your way with special handling of `'/'` made more sense - the slash obviously determines path topology, if we merely sort it according to the ASCII...