-
-
Notifications
You must be signed in to change notification settings - Fork 713
refactor: add no-nested-component-definitions
rule to eslint migration
#6941
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
Conversation
🦋 Changeset detectedLatest commit: fb983b0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 13 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
19c4280
to
1424d4c
Compare
CodSpeed Performance ReportMerging #6941 will not alter performanceComparing Summary
Footnotes |
name: "noNestedComponentDefinitions", | ||
language: "jsx", | ||
sources: &[RuleSource::EslintReactXyz("no-nested-components").same()], | ||
sources: &[RuleSource::EslintReactXyz("no-nested-component-definitions").same()], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would make sense to keep the old name around too, in case users are migrating from a version that uses the previous name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I updated to use both old and new one.
version: "2.0.0",
name: "noNestedComponentDefinitions",
language: "jsx",
- sources: &[RuleSource::EslintReactXyz("no-nested-components").same()],
+ sources: &[
+ RuleSource::EslintReactXyz("no-nested-components").same(),
+ RuleSource::EslintReactXyz("no-nested-component-definitions").same(),
+ ],
recommended: false,
domains: &[RuleDomain::React],
severity: Severity::Error,
4cb04a0
to
6d56c25
Compare
@JamBalaya56562 you need to run Also, I believe it would be useful to create a changeset, because we fixed the docs and the migration :) |
6d56c25
to
a1550cd
Compare
a1550cd
to
d77dad2
Compare
no-nested-components
ruleno-nested-component-definition
rule to eslint migration
no-nested-component-definition
rule to eslint migrationno-nested-component-definitions
rule to eslint migration
Thank you so much! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you 😊
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Co-authored-by: Naoki Ikeguchi <me@s6n.jp>
Co-authored-by: Carson McManus <dyc3@users.noreply.github.com>
Summary
Add the ESLint React
no-nested-component-definitions
rule across migration and lint rule declarationEnhancements:
Why?
#990 renamed
no-nested-components
rule tono-nested-component-definitions
and updated related docs.