Brandon Mills

@JounQin I haven’t really gotten comfortable with the API we’ve been discussing in this issue. However, #14745 looks to be an adjacent use case, and it gave me an idea:...

This only auto-closed because I forgot to self-assign. Sorry about that.

We decided in the TSC meeting that we'd like to provide a solution to this. We can discuss possible options here on the issue. One option is replicating `eslint.lintText()`'s [`warnIgnored`...

Agreed this looks like a regression. I still have the release issue open, so while this isn’t a show-stopper that absolutely requires a patch release, if there’s a fix available...

This use case sounds very similar to #14198. Here, we want to lint a JS file _and_ separately lint expressions from JSDoc comments. #14198 wants to lint a Markdown file...

1. We shouldn’t be special casing JS files in processor handling. Returning the file’s entire text as an unnamed first block in @JounQin‘s example works around the “lint file XOR...

Aha, now I think I see how Markdown figures in. When you see an `@example` in a JSDoc comment, you want to ESLint to treat the example’s contents as Markdown,...

Thank you for getting me up to speed here. As I understand it, there are two limitations of the processor API that would need to be resolved before it’s a...

Yes, assuming there are no objections, I need to write an RFC that will allow linting a file and extracting its blocks with a processor and linting those too. There's...

I looked at standardizing the existing workaround in which `preprocess()` returns the full file text as the first "block" in the array. However, that mean would mean the processor and...