for sure, it's a great skill to learn and once you do it's actually a ton of fun! The docs on eslint are a good placed to start. A thing to note, the function names are AST selectors (think CSS selectors, but for code). that may seem strange, but consider this code:

const foo = { "bar": function() {} };

then consider that this function can use the shorthand notation like this:

const foo = { "bar"() {} };

and if you have a variable you can do this:

const x = "baz";

const foo = { [`bar ${x}`]() {} }

which could be called like this:

foo["bar baz"]();

an eslint rule uses that pattern (as many of the rules in this plugin do) to declaratively handle various use cases. So for example, if you wanted a rule to match all CallExpressions you would do

{ "CallExpression"(node) { ... } }

if you wanted a rule to match all call expressions that were named 'foo' (as in foo()), you would do this:

{"CallExpression[callee.name=foo]"(node) { ... }}

(that might look familiar if you've ever written a CSS selector like div[role=button], that's because it is. :)
You might be wondering how you can know what all the various types and properties etc, don't worry astexplorer.net has you covered there. It's a great tool and this entire plugin was written using it. It's like a dom-inspector for code, and you can play around with rules in real time (among other things).

match toBe(null) and possibly toEqual(null) in addition to toBeNull #152

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

match `toBe(null)` and possibly `toEqual(null)` in addition to `toBeNull` #152