classic styling?

[quantuminformation]

seen

might be better for users to see it like

[metonym]

Agreed. Open to PRs in this regard.

~Also, another idea would be to make the component "styleless" by default, leaving styling up to the consumer.~

Thinking back on it, the original intent was to make this component "styleless." If you're after the classic "switch" look, I'd suggest looking at something like svelte-switch.

[quantuminformation]

it didnt work for me and its too much bloat from react

[metonym]

@quantuminformation in which case I'm open to exploring the classic UI

Thinking aloud here... I see the benefit of having a classic UI look while also giving the freedom to style it however way you want it. Going even further, the Toggle could be "renderless" (i.e. a slot that passes state as props)

• Toggle base export (unstyled)
• ToggleSwitch (classic UI)

[quantuminformation]

nice one thx, I think people like me are just lazy and want it to look good and you to do the thinking

[metonym]

@quantuminformation svelte-toggle has been redesigned and released in v1.0.0. It incorporates changes that address several issues you've raised. Let me know if you encounter any issues.

The demo contains example use cases.

PR #5

• refactor default toggle styles to conform to the classic "switch" UI for boolean states (#2)
• allow Toggle UI colors to be customized (switchColor, toggledColor, untoggledColor) (#3)
• allow label to be visually hidden (set hideLabel to true) (#4)
• default label text is changed from "Toggle label" to "Label"
• make on/off labels optional (by default they're undefined)
• add small variant for Toggle switch size
• extract core component logic into standalone ToggleCore which instruments the accessibility aspects (this component is "renderless" in that it does not have any styles or markup) refactor default Toggle to use ToggleCore

Breaking Changes

• on / off props are optional and must be truthy to use named slots

[quantuminformation]

Wow you are fast man! great work!