Fix code examples for VisualDivider component#284
Merged
Conversation
MelissaAutumn
approved these changes
May 19, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changed?
This change improves the demo code examples and enhances the stories for the
VisualDividercomponent. Component names and HTML attributes are now in dash-case. Reactivity for the default story is kept intact. Also the stories got some more text flow context to better visualize the component.Additionally a style issue was fixed, where the divider disappeared due to flex items letting it shrink.
Why?
More organized and consistent documentation.
Limitations and Notes
None.
Applicable Issues
Closes #269
Screenshots
Before:
After: