fix!: use distinct names for label props and slots (svelte 5 fix) #2408
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spburtsev
force-pushed
the
distinct-label-children
branch
from
8b57958 to
3806960
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #2105
Breaking changes:
labelTextslot renamed tolabelChildrento resolve Svelte 5 errors when passing snippetsIn Svelte 5, having both a
labelTextprop andlabelTextslot causes the static analyzer to flag errors when using snippet syntax. Renaming the slot eliminates this error and creates a clearer distinction between text-only labels (prop) and rich content labels (slot/snippet).