Skip to content

ci(lint): fix react/no-unknown-property eslint violations#4582

Merged
erikgb merged 1 commit intoweaveworks:mainfrom
erikgb:no-unknown-property
Jan 19, 2025
Merged

ci(lint): fix react/no-unknown-property eslint violations#4582
erikgb merged 1 commit intoweaveworks:mainfrom
erikgb:no-unknown-property

Conversation

@erikgb
Copy link
Copy Markdown
Contributor

@erikgb erikgb commented Jan 19, 2025

Closes

What changed?

Fix and enable the react/no-unknown-property eslint rule.

Why was this change made?

Follow-up after introducing react eslint. The react/no-unknown-property rule is a recommended rule.

How was this change implemented?

How did you validate the change?

Release notes

Documentation Changes

@erikgb erikgb requested a review from a team January 19, 2025 21:07
@erikgb erikgb enabled auto-merge (rebase) January 19, 2025 21:07
Comment thread eslint.config.mjs

"react/display-name": 0,
"react/no-children-prop": 0,
"react/no-unknown-property": 0,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

did you mean to still remove this? Looks like you fixed the issues it related to so maybe then leave it in place?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes, my intent was to remove it - since it currently turns the rule off. It is turned on by the recommended react eslint rules.

@erikgb erikgb merged commit 714e125 into weaveworks:main Jan 19, 2025
This was referenced Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants