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: migrated snippet shadowing prop and let directive removal #13679

Merged
merged 3 commits into from
Oct 18, 2024

Conversation

paoloricciuti
Copy link
Member

Svelte 5 rewrite

Closes #13665

While fixing i also noticed that we were incorrectly removing the let directive in the case where we don't migrate the slot if the let directive were there before the name of the slot.

Please note that the Svelte codebase is currently being rewritten for Svelte 5. Changes should target Svelte 5, which lives on the default branch (main).

If your PR concerns Svelte 4 (including updates to svelte.dev.docs), please ensure the base branch is svelte-4 and not main.

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

Copy link

changeset-bot bot commented Oct 18, 2024

🦋 Changeset detected

Latest commit: 3dc5116

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

Copy link
Member

@benmccann benmccann left a comment

Choose a reason for hiding this comment

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

i'm curious, could you just add stuff the queue and flush it at the very end? the code might be simpler if that's possible, but I'm not sure if it would cause things to break and the intermediate flushes are required

if that's not possible then I think we could merge this

@paoloricciuti
Copy link
Member Author

i'm curious, could you just add stuff the queue and flush it at the very end? the code might be simpler if that's possible, but I'm not sure if it would cause things to break and the intermediate flushes are required

if that's not possible then I think we could merge this

Yeah it should be doable...it was just to prevent pushing and then looping if we find the name immediately (which should be the common case imho). Should I do it?

@benmccann
Copy link
Member

I think it'd end up being a nice code simplification

@paoloricciuti
Copy link
Member Author

I think it'd end up being a nice code simplification

Aight...let me do it quickly

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.

migrate: snippet shadowing prop with same name
2 participants