fix: use strict equality for key block comparisons in runes mode#14285
fix: use strict equality for key block comparisons in runes mode#14285dummdidumm merged 1 commit intomainfrom
Conversation
🦋 Changeset detectedLatest commit: f054a92 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
|
|
preview: https://svelte-dev-git-preview-svelte-14285-svelte.vercel.app/ this is an automated message |
|
this doesn't seem to fix the example (simplified to
actually, the test in this pr also works fine (does not re-render) in the latest released version 5.1.16 |
|
yeah, the repro in the issue is incorrect because {#key data.current.component}
<data.current.component state={data.current.state} />
{/key}...and the test case in this PR simulates that with a |
|
🤦♂️ right, totally spaced out, they're deeply proxified except for anything other than simple objects or arrays. |
closes #14283
Before submitting the PR, please make sure you do the following
feat:,fix:,chore:, ordocs:.Tests and linting
pnpm testand lint the project withpnpm lint