-
When submitting a form I would expect the SvelteKit `$navigation` store to be updated and to have a type of `form` as described at https://kit.svelte.dev/docs/types#public-types-navigation.
But sub…
-
**Description**
I want to preface with saying this is non-blocking as the issues are type related and can be ignored until a permanent fix is implemented. All the logic for this works beautifully and…
-
**Description**
Zod allows for chaining regex, but when used with superforms it gives the error: "Only one regex is allowed per field".
**If applicable, a MRE**
https://stackblitz.com/edit/svelte…
-
Hello, I have a problem using dateProxy, but in general with any kind of proxy.
When I try to use a dateProxy like
```
const startAt = dateProxy(form, 'startAt', { format: 'datetime-local' });…
-
As per HTML spec, values of disabled inputs should not be submitted. but I observed they are getting submitted to backend.
is this a bug?
Server logs
## reproduce
https://github.com…
-
Current behaviour:
```js
setError(form, '', 'This is an error!');
```
Desired behaviour:
```js
setError(form, 'This is an error!');
```
I believe this can be achieved by checking if the seco…
-
**Description**
I am using a Superform inside a navbar that the user has access to. This navbar is located in the Layout. I noticed that if I have a normal run of the mill Svelte progressively enhanc…
-
**Description**
Thank you so much for this excellent package!
I am very pleased w/ it, and had a working project set up w/ SuperForms 0.6.18, and several forms.
Am just now going thru to upda…
-
**Description**
When using client side validators the error store shows some inconsistent behavior before and after form submits.
Looking at these two examples:
---
### The error store after …
-
Is there an escape hatch, or recommended workaround for using zod schemas with unsupported features, like `.pipe()` or `.refine()`?
I understand there may be more boiler plate I have to take care o…