Skip to content

Instantly share code, notes, and snippets.

View yatki's full-sized avatar
🖖
Cheers,

Mehmet Yatkı yatki

🖖
Cheers,
View GitHub Profile
@yatki
yatki / .eslintrc
Last active October 29, 2019 13:46 — forked from jrencz/.eslintrc
Useful set of words for eslint-plugin-spellcheck
{
"plugins": [
"spellcheck"
],
"rules":
// Spellcheck
//
"spellcheck/spell-checker": ["warn", {
"skipWords": [
// own names
@yatki
yatki / writing-eslint-rule.md
Created January 7, 2019 15:13 — forked from sindresorhus/writing-eslint-rule.md
Gettings started writing a ESLint rule

Gettings started writing a ESLint rule

First, take a look at the ESLint rule documentation. Just skim it for now. It's very long and boring. You can come back to it later.

ESLint rules works on the AST (Abstract Syntax Tree) representation of the code. In short, this is a tree structure that describes the code in a very verbose form. ESLint walks this tree and rules can subscribe to be notified when it hits a specific node type, like a Literal type, which could be the "hello" part of const welcome = "hello";.

Go ahead and play around with some code in AST Explorer (Make sure the parser is espree). It's a great tool!

Here are some good articles on the subject (ignore the scaffolding parts):