📎 Implement noNestedComponentDefinitions

[dyc3]

Description

Port no-nested-components from @eslint-react/eslint-plugin.

The rule sources should include @eslint-react/eslint-plugin and eslint-plugin-react-x.

Source: https://eslint-react.xyz/docs/rules/no-nested-components

Want to contribute? Lets you know you are interested! We will assign you to the issue to prevent several people to work on the same issue. Don't worry, we can unassign you later if you are no longer interested in the issue! Read our contributing guide and analyzer contributing guide.

[ematipico]

Personal note: I thought the name of the rule was preventing the use of nested components e.g <Foo><Bar /></Foo>

Maybe the proposed name is fine. I would go for noNestedDeclaredComponents, or noNestedComponentDefinitions. They are way longer though

[dyc3]

I like noNestedComponentDefinitions

[Atishay-J]

Hi @dyc3 , I am interested in this, can you assign this to me?

[dyc3]

@Atishay-J Sure! Be sure to make your PR against the next branch.

[Atishay-J]

sure! will do

[Atishay-J]

Hi @dyc3 ,
I’m unable to continue with this due to unforeseen reasons.
Please feel free to reassign it.
Apologies for the inconvenience

[mehm8128]

@ematipico @dyc3
Hi, I'm interested in this issue, could you assign it to me?
And I want to confirm one thing. It seems no-nested-components rule in ESLint even covers class component, React.createElement, and nestedComponentInProps, should we cover it?
I've never implemented new lint rule in Biome, so I'm not sure if I would be able to completely cover these cases.

[dyc3]

Yeah, we should cover those. Give it a shot! It's OK if you don't want to account for all of those cases in the first PR, you can make multiple PRs for this.

[mehm8128]

OK, thank you. I'll try it!