-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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: use dynamic components in root.svelte
instead of svelte:component
for svelte 5
#12584
fix: use dynamic components in root.svelte
instead of svelte:component
for svelte 5
#12584
Conversation
…nent` for svelte 5
🦋 Changeset detectedLatest commit: 9cbeff4 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 |
${ | ||
isSvelte5Plus() | ||
? `<!-- svelte-ignore binding_property_non_reactive --> | ||
<Piramid_${l} bind:this={components[${l}]} data={data_${l}} {form} />` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Piramid or Pyramid ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh...will rename
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pyramyd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:close_snype:
Closes #12573
Again i'm not really sure if and where i should add a test for this. Also for the moment i did not rename
constructors
to something else in svelte 5 because there was still the possibility to share some code but i'm willing to completely split the two branches if we feel like.Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.Edits