Skip to content

fix: resolved issue of $props incorrectly detected as store when using variables named after runes like $props and props #692

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Mar 27, 2025

Conversation

baseballyama
Copy link
Member

Copy link

changeset-bot bot commented Mar 26, 2025

🦋 Changeset detected

Latest commit: b2abfa0

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

This PR includes changesets to release 1 package
Name Type
svelte-eslint-parser 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

@baseballyama baseballyama changed the title fix: resolved an issue where $props was incorrectly recognized as astore when variables shared names with runes, such as $props and props. fix: resolved an issue where $props was incorrectly recognized as astore when variables shared names with runes, such as $props and props Mar 26, 2025
Copy link
Contributor

github-actions bot commented Mar 26, 2025

Try the Instant Preview in Online Playground

ESLint Online Playground

Install the Instant Preview to Your Local

npm i https://pkg.pr.new/svelte-eslint-parser@692

Published Instant Preview Packages:

View Commit

@baseballyama baseballyama changed the title fix: resolved an issue where $props was incorrectly recognized as astore when variables shared names with runes, such as $props and props fix: resolved issue of $props incorrectly detected as store when using variables named after runes like $props and props Mar 26, 2025
… store when variables shared names with runes, such as `$props` and `props`.
@coveralls
Copy link

Pull Request Test Coverage Report for Build 14086358686

Details

  • 13 of 13 (100.0%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.004%) to 94.659%

Totals Coverage Status
Change from base Build 14050456749: 0.004%
Covered Lines: 10478
Relevant Lines: 10945

💛 - Coveralls

@baseballyama baseballyama marked this pull request as draft March 26, 2025 15:02
@baseballyama baseballyama marked this pull request as ready for review March 27, 2025 01:29
@baseballyama
Copy link
Member Author

I confirmed this PR fixes both issues in my project.

Copy link
Member

@ota-meshi ota-meshi left a comment

Choose a reason for hiding this comment

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

LGTM! Thank you!

@ota-meshi ota-meshi merged commit 1c533d8 into main Mar 27, 2025
12 of 13 checks passed
@ota-meshi ota-meshi deleted the fix/runes-scope branch March 27, 2025 01:46
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

no-unused-props reports false positive @typescript-eslint/no-use-before-define reports $props unepectedly
3 participants