Pablo Berganza

Going further into why I'm proposing an API that uses the validity states as key rather than the fields: 1. For most use-cases, the validation message does not need to...

So we are going by levels of possible edge cases. 1. The default behaviour, which would be the path with less friction, would be a simple call to `validator()` without...

Regarding testing: Besides `reporter-svelte` everything is tested as VanillaJS with DOM testing library in some cases. Felte's core is quite framework agnostic since the `form` action only needs to receive...

I understand your concern here. But as far as I can see this can still be considered an _edge_ case. Even when context is needed, most of the times it...

The reason the validation messages functionality is not higher up is that the `core` is completely decoupled to what validation strategy you're using. Third-party libraries each one have their own...

I'd argue with your first point: Felte _does_ support nesting in its core. Using named `fieldset` elements or naming such as `name="account.username"` does create a nested data structure within Felte's...

Hey! I personally haven't used the beta version of yup. As long as the `validate` API will not have any breaking changes it should be no issue to add these....

Hey! This seems to be fixed by using `type FormData = { /*... */ }` instead of `interface FormData`. This seems to be due to how [interfaces work](https://github.com/microsoft/TypeScript/issues/41518) and how...

The reason why it is currently `unknown` is that, when making this feature, I assumed the source of your data could be almost anything. E.g. completely changing the shape of...

Hey, sorry for the delay! This is to be expected right now, unfortunately. `isValid` is tied to the `validate` function in the configuration (or if you're using a validator). There's...