Bryan Mishkin
Bryan Mishkin
I put together an RFC! * https://github.com/eslint/rfcs/pull/116
Makes sense to count these. I'm used to test coverage tools counting them as separate branches.
I'd love to use a rule's `meta.deprecated` and `meta.replacedBy` properties to indicate the replacement rule when a rule is moved out of core. I actually wrote up a proposal of...
I think it's a neat idea. While ESLint hasn't been prescriptive about requiring specific rule test cases thus far, the testing of fixability/suggestions is a good example of important test...
Just to explore the design of such a feature some more, I see a few options: 1. A test failure, thus making this a breaking change. 2. A helpful warning...
Not stale, would be interested to see more exploration here.
What does a "custom wrapper" entail? It looks like there are some good ideas in that list. It may be worth creating a table indicating some more data-points for each:...
Allowing arbitrary `meta` could be sufficient as the solution (as opposed to just allowing `meta.docs` as I was originally suggesting). I'm open to this if others prefer it. The downside...
There seem to be some conflicting thoughts so far about whether user-defined properties should go in `meta` (where some official properties are already located) or `meta.docs`. I would find it...
As mentioned, we do use Markdownlint, which provides a lot of consistency benefits for our docs already. As for Prettier, I'm generally in favor of using Prettier as much as...