`eslint-plugin-mdx` won't work along with `eslint-plugin-markdown` about eslint-mdx HOT 6 CLOSED

They're definitely not same. eslint-plugin-mdx aims to lint .mdx files without inside codes, while eslint-plugin-markdown aims to lint inside codes.

Maybe you need two eslint config to lint .md/.mdx twice if you'd like to lint inside codes.

from eslint-mdx.

Sure they target different things, that's why I expect eslint-plugin-mdx to work fine in my use case.

My point is eslint-plugin-mdx won't work with processor for eslint-plugin-markdown enabled while eslint-plugin-markdown works just fine with or without eslint-plugin-mdx.

And I believe using eslint-plugin-markdown along with eslint-plugin-mdx is a very common use case.

Anyway, I'll see if I can find what's going on under the hood.

from eslint-mdx.

I'm closing this as it's expected as per eslint/eslint-plugin-markdown#134, i.e., we can't lint those code inside code blocks in .mdx files with eslint-plugin-markdown.

@JounQin One last question, any plan to support linting code inside code blocks now that we can't use it together with eslint-plugin-markdown? It seems to be possible.

from eslint-mdx.

The mdx core team is working on v2 and will pasring mdx as estree directly, so such changes are not going to happen soon, but you're free to share ideas about the possible implementation.

from eslint-mdx.

I just get an idea that we can already get code blocks by ourselves, so it should be possible to lint them by eslint-plugin-mdx itself.

What means we will never be compatible with eslint-plugin-markdown, but we can support code blocks.

It should not be difficult, I'll get started soon when I'm free.

see #278

from eslint-mdx.

reopen in favor of eslint/eslint-plugin-markdown#178 and #283

from eslint-mdx.