feat: add support for the strategy parameter in component-name-unique rule - #3011
Open
harshit078 wants to merge 8 commits into
Open
feat: add support for the strategy parameter in component-name-unique rule#3011harshit078 wants to merge 8 commits into
harshit078 wants to merge 8 commits into
Conversation
🦋 Changeset detectedLatest commit: 12f8387 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 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 |
Contributor
Performance Benchmark (Lower is Faster)
|
harshit078
marked this pull request as ready for review
August 5, 2026 07:52
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 8cbffec. Configure here.
Member
|
Interesting idea! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What/Why/How?
#2898
Reference
Testing
Screenshots (optional)
Check yourself
Security
Note
Low Risk
Lint and bundle naming alignment with shared utility; behavior is covered by new tests and defaults preserve existing basename behavior.
Overview
Adds a
strategyoption (basename|title, defaultbasename) to thecomponent-name-uniquelint rule so uniqueness checks mirrorbundle --component-names-strategy.With
title, externally referenced schemas are keyed by PascalCase-sanitizedtitle(same as bundling); same basename with different titles no longer collide, while identical titles across files still fail. Schemas withouttitlefall back to basename/file naming; rootcomponents/schemaskeys are unchanged.componentNameFromTitleis shared betweenbundle-visitorand the rule (replacing inline logic in the visitor). Docs forbundleandcomponent-name-uniquecross-link the matching settings.Reviewed by Cursor Bugbot for commit 12f8387. Bugbot is set up for automated code reviews on this repo. Configure here.