Consider all-uppercase exports as components about eslint-plugin-react-refresh HOT 4 CLOSED

Yeah when I wrote it the first time I knew this could be improve by looking at what is the value type. I though I would need type info from eslint-typescript but actually I think allowing any function and disabling the rest should be ok. I will change this :)

from eslint-plugin-react-refresh.

Return value analyzation would be awesome, yes.

from eslint-plugin-react-refresh.

The rule is still giving me trouble when the component is wrapped:

These work:

export function SVG() {
  return <svg/>;
}

export const SVG = () => {
  return <svg/>;
};

These all fail:

export const SVG = forwardRef(() => {
  return <svg/>;
});

export const SVG = memo(forwardRef(() => {
  return <svg/>;
}));

export const SVG = memo(forwardRef(function SVG() {
  return <svg/>;
}));

from eslint-plugin-react-refresh.

Added in 0.4.1

(I've decided to not use type analysis because this could block a lot of people (not the default with TS-ESLint), so I need to add cases one by one)

from eslint-plugin-react-refresh.