You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+10-10
Original file line number
Diff line number
Diff line change
@@ -6,26 +6,26 @@ Thanks for your interest in helping out! Here are a **few** _weird_ tricks to ~~
6
6
7
7
When opening an [issue](#issues):
8
8
9
-
-[ ] search open/closed issues
10
-
-[ ] discuss bug/enhancement in new or old issue
9
+
-[ ] search open/closed issues
10
+
-[ ] discuss bug/enhancement in new or old issue
11
11
12
12
[PR](#prs) time:
13
13
14
-
-[ ] write tests
15
-
-[ ] implement feature/fix bug
16
-
-[ ] update docs
17
-
-[ ] make a note in change log
14
+
-[ ] write tests
15
+
-[ ] implement feature/fix bug
16
+
-[ ] update docs
17
+
-[ ] make a note in change log
18
18
19
19
Remember, you don't need to do it all yourself; any of these are helpful! 😎
20
20
21
21
## How to get started
22
22
23
23
If you are new to `eslint`, below are a few resources that will help you to familiarize yourself with the project.
24
24
25
-
- Watch [this presentation](https://www.youtube.com/watch?v=2W9tUnALrLg) to learn the fundamental concept of Abstract Syntax Trees (AST) and the way `eslint` works under the hood.
26
-
- Familiarize yourself with the [AST explorer](https://astexplorer.net/) tool. Look into rules in `docs/rules`, create patterns in the rules, then analyze its AST.
27
-
- Explore the blog posts on how to create a custom rule. [One blog post](https://blog.yonatan.dev/writing-a-custom-eslint-rule-to-spot-undeclared-props/). [Second blog post](https://betterprogramming.pub/creating-custom-eslint-rules-cdc579694608).
28
-
- Read the official `eslint`[developer guide](https://eslint.org/docs/latest/developer-guide/architecture/).
25
+
- Watch [this presentation](https://www.youtube.com/watch?v=2W9tUnALrLg) to learn the fundamental concept of Abstract Syntax Trees (AST) and the way `eslint` works under the hood.
26
+
- Familiarize yourself with the [AST explorer](https://astexplorer.net/) tool. Look into rules in `docs/rules`, create patterns in the rules, then analyze its AST.
27
+
- Explore the blog posts on how to create a custom rule. [One blog post](https://blog.yonatan.dev/writing-a-custom-eslint-rule-to-spot-undeclared-props/). [Second blog post](https://betterprogramming.pub/creating-custom-eslint-rules-cdc579694608).
28
+
- Read the official `eslint`[developer guide](https://eslint.org/docs/latest/developer-guide/architecture/).
With the advent of module bundlers and the current state of modules and module
160
160
syntax specs, it's not always obvious where `import x from 'module'` should look
@@ -175,7 +175,7 @@ resolvers are just npm packages, so [third party packages are supported](https:/
175
175
176
176
You can reference resolvers in several ways (in order of precedence):
177
177
178
-
- as a conventional `eslint-import-resolver` name, like `eslint-import-resolver-foo`:
178
+
- as a conventional `eslint-import-resolver` name, like `eslint-import-resolver-foo`:
179
179
180
180
```yaml
181
181
# .eslintrc.yml
@@ -195,7 +195,7 @@ module.exports = {
195
195
}
196
196
```
197
197
198
-
- with a full npm module name, like `my-awesome-npm-module`:
198
+
- with a full npm module name, like `my-awesome-npm-module`:
199
199
200
200
```yaml
201
201
# .eslintrc.yml
@@ -214,7 +214,7 @@ module.exports = {
214
214
}
215
215
```
216
216
217
-
- with a filesystem path to resolver, defined in this example as a `computed property` name:
217
+
- with a filesystem path to resolver, defined in this example as a `computed property` name:
218
218
219
219
```js
220
220
// .eslintrc.js
@@ -336,11 +336,11 @@ If you are using `yarn` PnP as your package manager, add the `.yarn` folder and
336
336
337
337
Each item in this array is either a folder's name, its subpath, or its absolute prefix path:
338
338
339
-
- `jspm_modules`will match any file or folder named `jspm_modules` or which has a direct or non-direct parent named `jspm_modules`, e.g. `/home/me/project/jspm_modules` or `/home/me/project/jspm_modules/some-pkg/index.js`.
339
+
- `jspm_modules`will match any file or folder named `jspm_modules` or which has a direct or non-direct parent named `jspm_modules`, e.g. `/home/me/project/jspm_modules` or `/home/me/project/jspm_modules/some-pkg/index.js`.
340
340
341
-
- `packages/core`will match any path that contains these two segments, for example `/home/me/project/packages/core/src/utils.js`.
341
+
- `packages/core`will match any path that contains these two segments, for example `/home/me/project/packages/core/src/utils.js`.
342
342
343
-
- `/home/me/project/packages`will only match files and directories inside this directory, and the directory itself.
343
+
- `/home/me/project/packages`will only match files and directories inside this directory, and the directory itself.
344
344
345
345
Please note that incomplete names are not allowed here so `components` won't match `bower_components` and `packages/ui` won't match `packages/ui-utils` (but will match `packages/ui/utils`).
Copy file name to clipboardExpand all lines: docs/rules/consistent-type-specifier-style.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -37,8 +37,8 @@ This rule includes a fixer that will automatically convert your specifiers to th
37
37
38
38
The rule accepts a single string option which may be one of:
39
39
40
-
-`'prefer-inline'` - enforces that named type-only specifiers are only ever written with an inline marker; and never as part of a top-level, type-only import.
41
-
-`'prefer-top-level'` - enforces that named type-only specifiers only ever written as part of a top-level, type-only import; and never with an inline marker.
40
+
-`'prefer-inline'` - enforces that named type-only specifiers are only ever written with an inline marker; and never as part of a top-level, type-only import.
41
+
-`'prefer-top-level'` - enforces that named type-only specifiers only ever written as part of a top-level, type-only import; and never with an inline marker.
42
42
43
43
By default the rule will use the `prefer-inline` option.
0 commit comments