[react/jsx-fragments] Enforce <Fragment> · jsx-eslint/eslint-plugin-react#2420

2019-09-26T14:34:42.000Z

I would like to enforce using ` ... ` instead of ` ... `. The fix option would mean to also add it to the imports if it hasn't been already. So these would be a warning: ```jsx import React from 'react'; export default Component = () => ( <>Foo ); ``` ```jsx import React from 'react'; export default Component = () => ( Foo ); ``` This would be the fix: (and should be fixable with `--fix`) ```jsx import React, { Fragment } from 'react'; export default Component = () => ( Foo ); ``` Is this achievable?

(7 comments) (12 reactions) (0 assignees)JavaScript (2,797 forks)batch import

help wantednew rule

Repository metrics

Stars: (8,630 stars)
PR merge metrics: (No merged PRs in 30d)

Description

I would like to enforce using <Fragment>...</Fragment> instead of <React.Fragment>...</React.Fragment>. The fix option would mean to also add it to the imports if it hasn't been already.

So these would be a warning:

import React from 'react';

export default Component = () => (
    <>Foo</>
);

import React from 'react';

export default Component = () => (
    <React.Fragment>Foo</React.Fragment>
);

This would be the fix: (and should be fixable with --fix)

import React, { Fragment } from 'react';

export default Component = () => (
    <Fragment>Foo</Fragment>
);

Is this achievable?

Contributor guide

Research direction: Learn how to create a new rule in eslint plugin react with autofix that transforms <React.Fragment> to <Fragment> and handles import addition. Study existing rules like jsx no target blank for patterns.
Tech stack: javascriptreact
Domain: developer experiencetooling
Issue type: Feature
Difficulty: 3
Estimated time: 1-2 days
Activity status: Active
Clarity: Clear
Prerequisites: Node.jsESLintGit
Newbie friendliness: 60

Repository metrics

Description

Contributor guide

Get fresh easy issues in your inbox.