feat: complex form data

[ulic75]

Overview

Adds support for converting formdata into complex objects and arrays, including arrays of objects. Thank you @fabian-hiller for your ModularForms which I based the code on.

Closes #3183

What is it?

• Feature / enhancement
• Docs / tests / types / typos

Description

Rewrote the formToObj function to support arrays of objects in addition to everything it supported before (objects, and simple arrays using []).

Checklist:

• My code follows the developer guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• Added new tests to cover the fix / functionality

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[netlify]

👷 Deploy request for qwik-insights pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	691fe42

[ulic75]

Looking into the failing tests.

[manucorporat]

Happy to merge this soon! amazing job

[tzdesign]

@ulic75 you don't know how many lines of code we can remove in our project.

Thank you so much

[tzdesign]

@manucorporat is this something we will see in one of the next releases?

[tzdesign]

@ulic75 I start implementing it with a e-commerce cart.

If I have a zodSchema like this:

export const addressSchema = z.object({
  company: z.string().optional(),
  workTitle: z.string().optional(),
  title: titleSchema.optional(),
  salutation: salutationSchema.optional(),
  firstname: z.string().min(2),
  lastname: z.string().min(2),
  street: z.string().min(2),
  streetNumber: z.string().min(1),
  zip: z.string().min(2),
  city: z.string().min(2),
  country: z.string().min(2),
  phone: z.string().optional(),
  mobile: z.string().optional(),
  fax: z.string().optional(),
  email: emailSchema.optional()
});

The errors I get back are not referenceable:

Zod knows the path:

Is it possible to implement the path here as well? This way you need a custom message for everything and flatten the arrays, but this will be a lot of work with multiple schemas.

[tzdesign]

@ulic75 ah, manu is just outputting error.flatten here.

I will check if I can fix it myself next week. If the default zodError always has a path, I would just join the path and we will end up with your dot notation.

[ulic75]

Thought it sounded more zod related. Sounds like a good thing to PR a fix for though.

[tzdesign]

@ulic75 I think a qwik reduce like this would be good:

  const errorByPath: Record<string, string> = result.error.issues.reduce(
    (acc, issue) => ({ ...acc, [issue.path.join('.')]: issue.message }),
    {} satisfies Record<string, string>
  );

I can't figure out how to put it in the DataValidator type yet. But when I have time next week, I will take a look.

[tzdesign]

@ulic75 Can you find your way around the action types? We have a complex cart type with addresses etc. and if cart.invoiceAddress.firstName fails, then you no longer know which field within cart has failed. The errors are flatten inside of cart.

cart: string[]