PascalCase constant is classified as a component

[githorse]

I think perhaps I'm seeing the converse of #26: I use PascalCase for my constants, and the plugin considers erroneously them to be components. An example that will trigger the rule:

export constant SomeConstant = 42 // ✗  [eslint] Fast refresh only works when a file only exports components ... 
export function someUtility() { return SomeConstant }

If I change that the capitalization to screaming snake, it passes:

export constant SOME_CONSTANT = 42 // ✓
export function someUtility() { return SOME_CONSTANT }

OK, I guess PascalCase is not the preferred convention here. But is there any global setting I'm missing that could easily prevent such constants from being flagged? (Using eslint-disable-next-line is more distracting than it's worth; if I have to do that I'll probably just switch to screaming snake, but that's not my preference.)

[ArnaudBarre]

Are you using a recent version? I don't have issue a warning with default options for this code:

export constant SomeConstant = 42
export function someUtility() { return SomeConstant }

This was probably buggy before 0.4.4, but now having PascalCase variable being init with something else than function or a function call should not be flagged as a React component.

[RazerM]

I had a file like this and the const RETRIES was being flagged, but renaming createRoutes to fit the component naming convention (e.g. to AppRoutes) fixed it.

const RETRIES = 3

export default function createRoutes() {
    return <App />
}

[ArnaudBarre]

React components should be PascalCase, this rules expect the convention to be followed like the official React hooks plugin