docs: clarify class attribute usage in Svelte templates #1404
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
I am a kinda beginner-ish dev. It took me over an hour to really test and find out this problem. Adding this comment would help new devs save time. Thanks.
|
@arif456 is attempting to deploy a commit to the Svelte Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Clarified class attribute usage in Svelte templates.
Added a note explaining how to correctly combine multiple class expressions inside class={} to avoid sequence expression issues in Runes mode. Includes examples of valid and invalid patterns for clarity.
I am a kinda beginner-ish dev. It took me over an hour to really test and find out this problem. Adding this comment would help new devs save time. Thanks.