jsx-eslint / eslint-plugin-react

React-specific linting rules for ESLint
MIT License
8.86k stars 2.76k forks source link

[Fix] `boolean-prop-naming`: literal TSIntersectionType not allow error fix #3705

Closed developer-bandi closed 3 months ago

developer-bandi commented 3 months ago

fix literal TSIntersectionType not allow error like below test case

      type Props = {
        enabled: boolean
      }
      type BaseProps = {
        semi: boolean
      }

      const Hello = (props: Props & BaseProps) => <div />;`

and left one error test case messioned in #3701 is exsit in test code

type Props = {
  enabled: boolean
}
const Hello: React.FC<Props> = (props) => <div />;

so I think this pr is merged, the issue #3285 can be closed.

codecov[bot] commented 3 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.76%. Comparing base (0abebc6) to head (a52e7eb).

:exclamation: Current head a52e7eb differs from pull request most recent head 48291e8. Consider uploading reports for the commit 48291e8 to get more accurate results

Additional details and impacted files ```diff @@ Coverage Diff @@ ## master #3705 +/- ## ======================================= Coverage 97.75% 97.76% ======================================= Files 133 133 Lines 9464 9467 +3 Branches 3466 3467 +1 ======================================= + Hits 9252 9255 +3 Misses 212 212 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.