|
1 | | -SublimeLinter-eslint 4.0.1 |
2 | | --------------------------- |
| 1 | +SublimeLinter-eslint 4.0.1 [BREAKING!] |
| 2 | +-------------------------------------- |
3 | 3 |
|
| 4 | +We switched to the new SL4 selectors. Which are awesome. |
4 | 5 |
|
5 | | -[BREAKING] again. We switched to the new SL4 selectors. What does that mean? |
6 | | -The whole `syntax` stuff and how I get this to work with `vue` or the |
7 | | -`eslint-plugin-html`, or even with "Javascript (super-next, next)" has been revisited. |
| 6 | +This replaces the old syntax_map as a ways to get this to work with "vue" |
| 7 | +or the "eslint-plugin-html", or even with "Javascript (babel, next)" etc. |
8 | 8 |
|
9 | | -By default, this plugin will now *only* select `source.js` |
10 | | -marked code, so it also lints embedded code in html. |
| 9 | +By default, this plugin will now *only* select "source.js", |
| 10 | +which should work with most vue/babel/next flavors and embedded code. |
11 | 11 |
|
12 | | -But this is finally pluggable. Go to your settings, the User settings or |
13 | | -project settings, and set it to e.g.: |
| 12 | +It's also configurable. Open your SublimeLinter settings and set it to e.g.: |
14 | 13 |
|
15 | | -``` |
16 | | - "eslint": { |
17 | | - "selector": "source.js, text.html.basic" |
18 | | - } |
| 14 | + "eslint": { |
| 15 | + "selector": "source.js, text.html.basic" |
| 16 | + } |
19 | 17 |
|
20 | | -``` |
21 | 18 |
|
22 | | -*iff* you have the `eslint-plugin-html` installed. Then the plugin will take |
23 | | -the whole file, not just the scripts tags and pass it to eslint. |
| 19 | +With the `eslint-plugin-html` installed, it will then take the whole file, |
| 20 | +not just the scripts tags, and pass it to eslint. |
| 21 | +Want it to grab `vue` files? "source.js, text.html.vue" for the win. |
24 | 22 |
|
25 | | -Want it to grab `vue` files: "source.js, text.html.vue" for the win. |
26 | 23 |
|
| 24 | +Other enhancements: |
27 | 25 |
|
28 | | -Enhancement: |
| 26 | +- We highlight errors that spread over multiple lines on ... multiple lines! |
| 27 | + So, if you have an empty "if" block, we highlight the entire block. |
29 | 28 |
|
30 | | -- We show errors that spread over multiple lines on ... multiple lines! |
31 | | - So, if you have an empty if block, we select the block not the if. |
| 29 | +- You can target different node version by setting, e.g.: |
| 30 | + "executable": ["nvm", "exec", "8.9", "path/to/eslint"] |
| 31 | + "executable": ["i/compiled/this/node", "path/to/eslint"] |
32 | 32 |
|
33 | | - |
34 | | -Tips and tricks: |
35 | | - |
36 | | -You can target different node version by setting, e.g.: |
37 | | - |
38 | | - `"executable": ["nvm", "exec", "8.9", "path/to/eslint"]` |
39 | | - |
40 | | - `"executable": ["i/compiled/this/node", "path/to/eslint"]` |
41 | | - |
42 | | - |
43 | | -You can tweak the execution environment: |
44 | | - |
45 | | - `"env": { |
46 | | - "PATH": "/some/additional/path/bin:$PATH" |
47 | | - }` |
| 33 | +- You can tweak the execution environment by setting, e.g.: |
| 34 | + "env": { |
| 35 | + "PATH": "/some/additional/path/bin:$PATH" |
| 36 | + } |
48 | 37 |
|
49 | 38 |
|
50 | 39 |
|
|
0 commit comments