[Bug]: The `forbidDefaultForRequired` option in the `react/require-default-props` rule does not work as expected about eslint-plugin-react

[ljharb]

Yes, with the react team’s very unwise and unfortunate decision in 18.3/19, we might as well add both things.

[ljharb]

The rule forbids default props, not default function parameters. In other words, the .defaultProps object attached to the component.

[vicasas]

@ljharb I understand that the current focus is solely on .defaultProps. However, is there any current or future support for performing a different type of validation?

The proposed validation would cover two aspects:

1. If there are required props, ensure they do not have a default value.
2. For non-required props, ensure they have a default value.

All of the above should always be validated with the function parameters.

[ljharb]

The first one seems like a great enhancement.

The second one, however, i don’t agree with and wouldn’t want to encourage people to do. Despite the react team’s position, defaultProps are much better than default arguments, because they’re introspectable from the outside (and they work on class components).

[vicasas]

@ljharb I understand your position regarding point 2, can we revisit it in the future for more feedback on this? I still think it would be nice to provide some support for this, maybe not encourage its use, but have it available as a utility.

Regarding point 1, I think it's great that it can be taken. Would this be validated on default arguments?

[vicasas]

@ljharb Regarding point 1, could we re-evaluate it? Facebook already made changes in React Dom (v18.3.0) to start throwing warnings when .defaultProps is used in functional components, but not for class ones.

See more: facebook/react@5894232