🐛 useCamelCase for React Components

[MichaReiser]

Environment information

Playground

What happened?

1. Created a react component named MarkdownRenderer
2. The useCamelCase rule reported a warning because of the component name

error[[js/useCamelCase](https://rome.tools/docs/lint/rules/useCamelCase/)]: Prefer functions names in camel case.
  ┌─ main.tsx:1:17
  │
1 │ export function MarkdownRenderer({
  │                 ^^^^^^^^^^^^^^^^

Expected result

Custom components must use upper case naming or React renders them as native HTML elements. Thus, applying the suggested fix isn't safe.

How the exact fix should look like is unclear to me. One option could be to not report a diagnostic if the function returns JSX but doing so has the downside that:

• I get a diagnostic when writing the function signature that only disappears when I wrote the function's body
• There's no sound way to detect if a function returns JSX

It thus, may mean that we shouldn't enabale the rule by default or, exclude functions.

Related issue typescript-eslint/typescript-eslint#2607

Code of Conduct

• I agree to follow Rome's Code of Conduct

[MichaReiser]

CC: @xunilrj for the work around correctness

[github-actions]

This issue is stale because it has been open 14 days with no activity.

[ematipico]

@xunilrj is this fixed by any chance?

[xunilrj]

Now, functions that are exported or are used in "new expressions" are ok. So yes.
See #3210.