Skip to content
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

fix: disallow accessing internal Svelte props #12207

Merged
merged 5 commits into from
Jun 28, 2024

Conversation

dummdidumm
Copy link
Member

closes #12184

should be merged after #12201 because it builds on that

Before submitting the PR, please make sure you do the following

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • Prefix your PR title with feat:, fix:, chore:, or docs:.
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests and linting

  • Run the tests with pnpm test and lint the project with pnpm lint

- allow to write `let props = $props()`
- optimize read access of props.x to use `$$props` argument directly; closes #11055
Copy link

changeset-bot bot commented Jun 27, 2024

🦋 Changeset detected

Latest commit: 72add9b

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

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

@@ -78,6 +78,10 @@

> Cannot use `$props()` more than once
## props_illegal_name

> Declaring or accessing a property starting with `$$` is illegal (they are reserved for Svelte internals)
Copy link
Contributor

Choose a reason for hiding this comment

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

Should it be prop, rather than property?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah I think that would be better because it more clearly hints that this is the prop-property, not some random property

@dummdidumm dummdidumm marked this pull request as ready for review June 28, 2024 07:20
Copy link
Contributor

@trueadm trueadm left a comment

Choose a reason for hiding this comment

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

Awesome

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.

Svelte 5: leaking private implementation details ($$events, $$slots)
2 participants