Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fix] no-object-type-as-default-prop: enable rule when multiple parameters #3768

Conversation

JulienR1
Copy link
Contributor

Fixes #3767 by allowing components with more than one parameter to be checked by no-object-type-as-default-prop.

Copy link
Member

@ljharb ljharb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems pretty straightforward, nice!

@ljharb ljharb force-pushed the bug/no-object-type-as-default-prop-issue-3767 branch from 62e7638 to 393bfa2 Compare June 13, 2024 06:07
@ljharb ljharb merged commit 393bfa2 into jsx-eslint:master Jun 13, 2024
327 checks passed
@JulienR1 JulienR1 deleted the bug/no-object-type-as-default-prop-issue-3767 branch June 13, 2024 14:07
Copy link

@RafaelJohn9 RafaelJohn9 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍nice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: react/no-object-type-as-default-prop is disabled when using a ref prop
3 participants