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
[](https://marketplace.visualstudio.com/items?itemName=JounQin.vscode-mdx)
29
47
30
48
[VSCode MDX]\: Integrates with [VSCode ESLint], syntaxes highlighting and error reporting.
31
49
@@ -110,7 +128,7 @@ npm i -D eslint-plugin-mdx
110
128
111
129
### mdx/no-jsx-html-comments
112
130
113
-
HTML style comments in jsx block is invalid, this rule will help you to fix it by transforming it to JSX style comments.
131
+
_Fixable_: HTML style comments in jsx block is invalid, this rule will help you to fix it by transforming it to JSX style comments.
114
132
115
133
### mdx/no-unescaped-entities
116
134
@@ -120,28 +138,30 @@ Inline JSX like `Inline <Component />` is supported by [MDX], but rule `react/no
120
138
121
139
[MDX] can render `jsx` block automatically without exporting them, but [ESLint] will report `no-unused-expressions` issue which could be unexpected, this rule is a replacement of it, so make sure that you've turned off the original `no-unused-expressions` rule.
122
140
123
-
##Limitation
141
+
### mdx/remark
124
142
125
-
> This parser/plugin can only handle ES syntaxes for you, markdown related syntaxes will just be ignored, you can use [markdownlint] or [remark-lint] to lint that part.
143
+
_possible fixable depends on your remark plugins_:
126
144
127
-
I have a very preliminary idea to integrate with[remark-lint].
145
+
Integration with [remark] plugins without [remark-lint], it will read[remark's configuration](https://github.com/remarkjs/remark/tree/master/packages/remark-cli#remark-cli) automatically via [cosmiconfig]. But `.remarkignore` will not be respected, you should use `.eslintignore` instead.
128
146
129
147
## Changelog
130
148
131
149
Detailed changes for each release are documented in [CHANGELOG.md](./CHANGELOG.md).
[](https://marketplace.visualstudio.com/items?itemName=JounQin.vscode-mdx)
29
47
30
48
[VSCode MDX]\: Integrates with [VSCode ESLint], syntaxes highlighting and error reporting.
31
49
@@ -110,7 +128,7 @@ npm i -D eslint-plugin-mdx
110
128
111
129
### mdx/no-jsx-html-comments
112
130
113
-
HTML style comments in jsx block is invalid, this rule will help you to fix it by transforming it to JSX style comments.
131
+
_Fixable_: HTML style comments in jsx block is invalid, this rule will help you to fix it by transforming it to JSX style comments.
114
132
115
133
### mdx/no-unescaped-entities
116
134
@@ -120,28 +138,30 @@ Inline JSX like `Inline <Component />` is supported by [MDX], but rule `react/no
120
138
121
139
[MDX] can render `jsx` block automatically without exporting them, but [ESLint] will report `no-unused-expressions` issue which could be unexpected, this rule is a replacement of it, so make sure that you've turned off the original `no-unused-expressions` rule.
122
140
123
-
##Limitation
141
+
### mdx/remark
124
142
125
-
> This parser/plugin can only handle ES syntaxes for you, markdown related syntaxes will just be ignored, you can use [markdownlint] or [remark-lint] to lint that part.
143
+
_possible fixable depends on your remark plugins_:
126
144
127
-
I have a very preliminary idea to integrate with[remark-lint].
145
+
Integration with [remark] plugins without [remark-lint], it will read[remark's configuration](https://github.com/remarkjs/remark/tree/master/packages/remark-cli#remark-cli) automatically via [cosmiconfig]. But `.remarkignore` will not be respected, you should use `.eslintignore` instead.
128
146
129
147
## Changelog
130
148
131
149
Detailed changes for each release are documented in [CHANGELOG.md](./CHANGELOG.md).
[](https://marketplace.visualstudio.com/items?itemName=JounQin.vscode-mdx)
29
47
30
48
[VSCode MDX]\: Integrates with [VSCode ESLint], syntaxes highlighting and error reporting.
31
49
@@ -110,7 +128,7 @@ npm i -D eslint-plugin-mdx
110
128
111
129
### mdx/no-jsx-html-comments
112
130
113
-
HTML style comments in jsx block is invalid, this rule will help you to fix it by transforming it to JSX style comments.
131
+
_Fixable_: HTML style comments in jsx block is invalid, this rule will help you to fix it by transforming it to JSX style comments.
114
132
115
133
### mdx/no-unescaped-entities
116
134
@@ -120,28 +138,30 @@ Inline JSX like `Inline <Component />` is supported by [MDX], but rule `react/no
120
138
121
139
[MDX] can render `jsx` block automatically without exporting them, but [ESLint] will report `no-unused-expressions` issue which could be unexpected, this rule is a replacement of it, so make sure that you've turned off the original `no-unused-expressions` rule.
122
140
123
-
##Limitation
141
+
### mdx/remark
124
142
125
-
> This parser/plugin can only handle ES syntaxes for you, markdown related syntaxes will just be ignored, you can use [markdownlint] or [remark-lint] to lint that part.
143
+
_possible fixable depends on your remark plugins_:
126
144
127
-
I have a very preliminary idea to integrate with[remark-lint].
145
+
Integration with [remark] plugins without [remark-lint], it will read[remark's configuration](https://github.com/remarkjs/remark/tree/master/packages/remark-cli#remark-cli) automatically via [cosmiconfig]. But `.remarkignore` will not be respected, you should use `.eslintignore` instead.
128
146
129
147
## Changelog
130
148
131
149
Detailed changes for each release are documented in [CHANGELOG.md](./CHANGELOG.md).
0 commit comments