Skip to content

Commit 714939b

Browse files
committed
docs: update roadmap and no-useless-fragment documentation
1 parent 7e70c16 commit 714939b

File tree

3 files changed

+53
-53
lines changed

3 files changed

+53
-53
lines changed

website/content/docs/roadmap.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ title: Roadmap
2424
### Add auto-fix feature to rules that can be auto-fixed safely
2525

2626
- [ ] `function-component-definition`
27-
- [ ] `no-useless-fragment`
27+
- [x] `no-useless-fragment`
2828
- [x] `prefer-shorthand-fragment`
2929
- [x] `prefer-react-namespace-import`
3030
- [x] `prefer-shorthand-boolean`

website/content/docs/rules/no-useless-fragment.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ react-x/no-useless-fragment
1616

1717
**Features**
1818

19-
`🔍` `⚙️`
19+
`🔍` `🔧` `⚙️`
2020

2121
**Presets**
2222

@@ -91,7 +91,7 @@ places like Typescript where `string` does not satisfy the expected return type
9191
of `JSX.Element`. A common workaround is to wrap the variable holding a string
9292
in a fragment and expression. To change this behaviour, use the `allowExpressions` option.
9393

94-
### Examples of correct code for single expressions in fragments:
94+
### Examples of correct code for single expressions in fragments
9595

9696
```tsx
9797
<>{foo}</>

0 commit comments

Comments
 (0)