Brett Zamir

Busy myself, so that'd be great on my end. Btw, one thing to note is that if jsdoc is added that is well-structured per [jsdoc-jsonschema](https://github.com/brettz9/jsdoc-jsonschema), you can use this tool...

[`c8`](https://github.com/bcoe/c8/) is working for me with `"type": "module"`.

Looks all good to me... Thanks!

> > If not allowing parsing which errs upon use of the JSON6 (or changing JSON6 to become a strict subset of JS), I would find it helpful to have...

Another difference (inspired by https://github.com/ota-meshi/eslint-plugin-jsonc/pull/7 -- which is included in a new release of the jsonc plugin which already supports some JSON6 parsing, btw) is: `- 8` works in ES...

> The documentation generated for `requestsPerSecond` is wrong. It's based on https://github.com/JMPerez/promise-throttle/blob/master/lib/main.js#L7 and it doesn't understand that requestsPerSecond is a property passed in the options object argument. Hi... Very useful...

Yes, I think we could allow any `settings.jsdoc.contexts` contexts to be automatically added though while still allowing those individual options--since a project might not want every rule to behave the...

While they are indeed all functions, projects often use them for distinct purposes. For example, some use arrow functions only within contexts like `forEach`, thus perhaps making them less desired...

> The schema you suggested seemed prone to abuse, it encourages people to write function in different syntax as a way to circumvent this rule. You speak about linting rules...

I think one thing we're both missing here is the fact that Selectors (driven within eslint by `esquery`) are pretty [powerful](https://eslint.org/docs/developer-guide/selectors) and users can already add them as `contexts`. For...