[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) (11 reactions) (0 assignees)JavaScript (8,630 stars) (2,797 forks)batch import

help wantednew rule

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

Tech stack: javascriptreact
Domain: tooling
Issue type: feature
Difficulty: 3
Estimated time: 1-3 hours
Activity status: stale
Clarity: clear
Prerequisites: ESLint plugin developmentAST basicsReact JSX
Newbie friendliness: 65
Research direction: Look at existing similar rules in `lib/rules/` for structure, e.g., `jsx no target blank`. Check issue comments (especially maintainer responses) for guidance. Focus on implementing a new rule that enforces the use of `<Fragment>` over alternatives, with auto fix to add imports. The implementation involves creating a rule file, tests in `tests/lib/rules/`, and documentation.