Switch onChange

[anton-johansson]

Hey peeps! I'm trying out the Switch component, but I'm having a hard time using onChange. How can I react to changes of the isChecked property? The onChange property fires a simple FormEvent<any> and I can't seem to reach the isChecked value... Ideas?

[with-heart]

Hi @anton-johansson! You'd want to use e.target.checked, as seen in this example: https://codesandbox.io/s/vibrant-johnson-lchqn?file=/src/App.tsx

[with-heart]

Oh, that explains it. Yeah TypeScript support is spotty at best on v0. It matches your type on v1:

chakra-ui/packages/checkbox/src/use-checkbox.ts

Lines 60 to 63 in acc6e16

	/**
	* The callback invoked when the checked state of the `Checkbox` changes..
	*/
	onChange?: (event: ChangeEvent<HTMLInputElement>) => void

[anton-johansson]

Allright, cool! But v1 is not released, is it?

[ljosberinn]

No, but it's encouraged to be used when you're just starting to build something with Chakra or are in an early phase. We have migration docs here: https://next.chakra-ui.com/docs/migration - please ensure to remove your lockfile as well as node_modules when migrating. Also you might need to update TypeScript (3.8.5 is min req but realistically there is no reason to not be on latest), @types/react as well as remove emotion dependencies (we'll add this info to the docs too).

[anton-johansson]

Thanks people! I'll migrate to v1. Do we have any estimate on when v1 will be released? I feel kinda weird about using a "non-stable" (it's probably stable, but you catch my drift) package.

EDIT: I assume 0.8.0 isn't really "stable" either, so it probably doesn't really matter. :D But would be great with an estimate anyway!

[ljosberinn]

Yes, we're fairly far along v1 so there shouldn't be any major bugs left.
At the current time it looks like we're seeing another rc to make sure everything we recently changed is stable and then release 👀