Milos Djermanovic

> > I'm also confused about what the RFC has to do with this issue. > > I understood that the RFC is about handling specific label patterns with the...

> I think this could make sense as an option, maybe a `--suppress-warnings` CLI option that enables this behavior when used with `--suppress-all` or `--suppress-rule`. Sounds good to me 👍

I agree this needs an RFC. At first glance, this seems like a simple change, but after thinking about it more, there are details we should discuss. For example, how...

The value of "parser" serialized in the URL is also `true`. Perhaps we could use a string value (`"@typescript-eslint/parser"`) to allow for adding more parsers in the future?

> > The value of "parser" serialized in the URL is also true. Perhaps we could use a string value ("@typescript-eslint/parser") to allow for adding more parsers in the future?...

> > "parser": true means that the "@typescript-eslint/parser" should be used. But that limits the Playground URLs to only one custom parser, and if we add more in the future,...

I support this proposal. I'm not sure if ESLlint should automatically turn off rules that don't apply to the given language or rather throw a descriptive error because end users'...

> 1. To determine if a rule will work for a given language. This actually relates more to the plugin language than it does the formal name of the language...

> My idea was that we'd look up from the rule like this: > > 1. Find the plugin in the config named `markdown`. If one doesn't exist, then search...

Prettier playground saves the issue body to the clipboard when it's too long: