Skip to content

fix: false positives for regular components in valid-compile/custom_element_props_identifier (#1241) #1243

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

zachstence
Copy link

Fixes #1241

My fix ensures we're only passing the customElement: true option to compile() when the code actually uses a customElement option (or the deprecated tag option).

Test case valid-compile/invalid/custom_element_props_identifier-errors tests the custom_element_props_identifier error
Test case valid-compile/valid/valid-custom-element-with-props-identifier tests the resolution of the custom_element_props_identifier error
Test case valid-compile/valid/no-false-custom_element_props_identifier-warning-without-custom-element tests my fix for the false-positive of the custom_element_props_identifier on a regular Svelte component (not a custom element)

Copy link

changeset-bot bot commented Jun 5, 2025

🦋 Changeset detected

Latest commit: cc28f3f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
eslint-plugin-svelte Patch

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

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.

False custom_element_props_identifier errors with no custom elements
1 participant