Mark Fayngersh
Mark Fayngersh
Hm, going to take a look...
Apologies if the bump is inappropriate, but I too would find value in being able to use the workspace TypeScript version with the Svelte extension. TypeScript 4.5 was just released...
This is a non-trivial blocker for me. Imagine the common filter experience where facets are stored in the URL as query strings. Whenever you'd call `NavManager.NavigateTo(NavManger.GetUriWithQueryParameter("color", "blue"))` the page will...
> Am I the only one having a problem with this issue even with the latest sveltekit & vite ? Check if you are returning any values in `return fail()`...
https://github.com/bryanmylee/svelte-render/pull/8
> I think the proposed behavior is pretty weird. I haven't used Zod nearly enough to have a good sense of what's idiomatic, so completely defer to your intuitions here,...
We're actually using Svelte Kit, which has the concept of Form Actions to handle `await request.formData()` server-side: https://kit.svelte.dev/docs/form-actions
> FormData isn't actually supported by Node or Bun. Maybe I'm misunderstanding, but the following works for me on Node v19: ```js // In `node` repl: > new FormData() ```
Some (not exhaustive) thoughts and ideas: `z.formData()` as a `z.object()` analog: ```ts const schema = z.formData({ channelType: z.enum(["public", "private"]), // formData.get("channelType") channelName: z.string().min(3), // formData.get("channelName") members: z.array(z.string()) // formData.getAll("members") })...
Prob safe to say same for SvelteKit.