Skip to content

fix: prevent whitespaces merging across component boundaries#12449

Merged
Rich-Harris merged 2 commits intomainfrom
whitespace-fuse-fix
Jul 15, 2024
Merged

fix: prevent whitespaces merging across component boundaries#12449
Rich-Harris merged 2 commits intomainfrom
whitespace-fuse-fix

Conversation

@dummdidumm
Copy link
Member

The logic that was there didn't take components into account. The underlying problem is that the parent isn't properly set to Fragment in all cases because of nested visit calls we do in some places.

Fixes #12447

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

The logic that was there didn't take components into account. The underlying problem is that the parent isn't properly set to `Fragment` in all cases because of nested `visit` calls we do in some places.

Fixes #12447
@changeset-bot
Copy link

changeset-bot bot commented Jul 15, 2024

🦋 Changeset detected

Latest commit: f43cf23

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

@Rich-Harris Rich-Harris merged commit 141e3e9 into main Jul 15, 2024
@Rich-Harris Rich-Harris deleted the whitespace-fuse-fix branch July 15, 2024 23:06
trueadm pushed a commit that referenced this pull request Jul 16, 2024
* fix: prevent whitespaces merging across component boundaries

The logic that was there didn't take components into account. The underlying problem is that the parent isn't properly set to `Fragment` in all cases because of nested `visit` calls we do in some places.

Fixes #12447

* update test
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.

Children duplication of list items rendered within components after v 5.0.0-next.179

3 participants