-
-
Notifications
You must be signed in to change notification settings - Fork 809
fix(noUnknownProperty): remove explicit ignore for composes
#8083
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: 672fa69 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 |
composes in noUnknownPropertycomposes
60ae11d to
672fa69
Compare
WalkthroughThe PR modifies the Suggested reviewers
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Forcepushed with different commit name, previous one was too long, fyi |
CodSpeed Performance ReportMerging #8083 will not alter performanceComparing Summary
Footnotes
|
|
Digged into failed tests, now it applies both parser and linter errors for the same line Is there any way to skip linting lines with parser errors already applied? Removed condition did exactly that, but it looks a bit hacky to me |
|
I believe the issue is that now the rule isn't skipping What you want to do is to extract the let source_type = ctx.source_type::<CssFileSource>();However, we don't save the |
|
I'll close it for now, will have another go after different PR |
Summary
Was working on another change in
noUnknownProperty, noticed thatcomposesproperty is already skipped withcssModulesenabled in parser configThe query is
Ast<CssGenericProperty>, and whencssModulesis enabled this property is parsed asCssComposesProperty, excluding it from the queryI think there is no need to allow
composesproperty when css modules parsing is disabledPrior PR when the check was added: #3217
Test Plan
Added separate test cases with and without
cssModulesenabledDocs
Not sure if any is required, but if so, please tell me and I'll update the website