[Feature]: <Switch/>

[christopherkindl]

What problem does this feature solve?

has been requested by a lot of users. Tremor team is also reworking their entire block section where they find a need for this component.

What does the proposed API look like?

Please use headless' switch for the underlying logic. See styling in the image below.

Explicit props:

• checked?: (value: string) => void;
• onChange?: (value: string) => void;
• color?: string // only for isChecked color
• id?: string
• name?: string
• error?: boolean
• errorMessage?: string
• disabled?: string

[mrkirthi-24]

Hi @christopherkindl, I would like to work on this issue

[christopherkindl]

Hi @mrkirthi-24, awesome, thank you! We just assigned you 🙂

[nicolasVenard]

Hey, I would also like to work on this issue, is that possible? Or do I have to find another one that's not assigned? 🙂

[mrkirthi-24]

@nicolasVenard I am working on this.

[christopherkindl]

@mrkirthi-24 just wanted to check-in whether you still want to tackle this? Otherwise happy to re-assign :)

[mrkirthi-24]

I apologize for the delay. I am working on it.

[christopherkindl]

Awesome, thank you! :)

[mrkirthi-24]

Hi @christopherkindl, I think disabled should be boolean?
And what should i do if explicit props "checked and onChange" are same as headless ui switch default props ? Should i change it??

[mrkirthi-24]

I am sorry but I cannot solve it

[mbauchet]

@AlexRousseau92

[AlexRousseau92]

Hello, i would like to work on this issue :)

[github-actions]

🎉 This issue has been resolved in version 3.10.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀