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: src/docs/guide/usage/linter/rules/jsx_a11y/anchor-is-valid.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,8 @@ All these anchor implementations indicate that the element is only used to execu
46
46
47
47
There are **many reasons** why an anchor should not have a logic and have a correct `href` attribute:
48
48
49
-
- it can disrupt the correct flow of the user navigation e.g. a user that wants to open the link in another tab, but the default "click" behaviour is prevented
49
+
- it can disrupt the correct flow of the user navigation e.g. a user that wants to open the link
50
+
in another tab, but the default "click" behaviour is prevented
50
51
- it can source of invalid links, and crawlers can't navigate the website, risking to penalise SEO ranking
Copy file name to clipboardExpand all lines: src/docs/guide/usage/linter/rules/react/jsx-curly-brace-presence.md
+13-3
Original file line number
Diff line number
Diff line change
@@ -163,7 +163,9 @@ that option for checking on both JSX props and children.
163
163
The fix also deals with template literals, strings with quotes, and
164
164
strings with escapes characters.
165
165
166
-
- If the rule is set to get rid of unnecessary curly braces and the template literal inside a JSX expression has no expression, it will throw a warning and be fixed with double quotes. For example:
166
+
- If the rule is set to get rid of unnecessary curly braces and the
167
+
template literal inside a JSX expression has no expression, it will
168
+
throw a warning and be fixed with double quotes. For example:
167
169
168
170
```jsx
169
171
<App prop={`Hello world`}>{`Hello world`}</App>
@@ -175,7 +177,10 @@ strings with escapes characters.
175
177
<App prop="Hello world">Hello world</App>
176
178
```
177
179
178
-
- If the rule is set to enforce curly braces and the strings have quotes, it will be fixed with double quotes for JSX children and the normal way for JSX attributes. Also, double quotes will be escaped in the fix.
180
+
- If the rule is set to enforce curly braces and the strings have
181
+
quotes, it will be fixed with double quotes for JSX children and the
182
+
normal way for JSX attributes. Also, double quotes will be escaped in
183
+
the fix.
179
184
180
185
For example:
181
186
@@ -189,7 +194,12 @@ strings with escapes characters.
- If the rule is set to get rid of unnecessary curly braces(JSX expression) and there are characters that need to be escaped in its JSX form, such as quote characters, [forbidden JSX text characters](https://facebook.github.io/jsx/), escaped characters and anything that looks like HTML entity names, the code will not be warned because the fix may make the code less readable.
197
+
- If the rule is set to get rid of unnecessary curly braces(JSX
198
+
expression) and there are characters that need to be escaped in its JSX
199
+
form, such as quote characters, [forbidden JSX text
200
+
characters](https://facebook.github.io/jsx/), escaped characters and
201
+
anything that looks like HTML entity names, the code will not be warned
202
+
because the fix may make the code less readable.
193
203
194
204
Examples of **correct** code for this rule, even when configured with `"never"`:
0 commit comments