Gustavo Fenilli

Sorry, I get what you mean now, the label of an button is actually the input because its the default slot, so you would style using the input. The case...

You can also do it via slots like you did, by getting the `context.classes`. https://formkit.link/9065aa6c99a1dc1112ef6f2e00915ad7

Think about a table that has many checkboxes ( select a row of it ) https://formkit.link/8b6b4dd962955d5c1c08c7680a0ae06d Or is there something I'm missing that could make this easier.

> The intended use (without the checked feature) is to be able to set your entire form state from the parent input, like the form and all the children are...

Maybe a `hasRule` utility function would work fine for that, so it would be easy to add this functionality via plugin by just checking if `hasRule('required')` and add to the...

I made a PR for it to be added to the utils #234. lets wait to see if the it passes and it gets added to the schema.

Mask is not currently a feature, but it is on the roadmap.

Mask is still not a feature, the team is working a lot to have the pro inputs delivered.

As it defaults to the default label/value behaviour if the specified key is not found, it does not need `:stop-option-map="true"` anymore, it just works with both APIs.

Added module augmentation to `FormKitOptionsPropExtensions` so `:options` do not give errors anymore.