Runtime Error with 'FormError' Execution in Development Mode using QwikJS v1.2.6 and ModularForms v0.18.1 about modular-forms HOT 10 OPEN

Does the problem exist when you downgrade to Qwik v1.1.5? Qwik v1.2.X is currently causing problems in general: BuilderIO/qwik#4789

from modular-forms.

Does the problem exist when you downgrade to Qwik v1.1.5? Qwik v1.2.X is currently causing problems in general: BuilderIO/qwik#4789

I have made a modification to the 'index.qwik.mjs' file, specifically to the 'formActionQrl' function. This change involves altering the 'trycatch' block, in such a way that the catch always sets the 'formActionStore' variable, which eliminates the error. I acknowledge that this is not the optimal solution, but it is a provisional measure to avoid delays in the development.

The problem that arises now is that, even though no errors are now presented and the 'formActionStore' variable is properly set with the error messages, etc., the errors are never displayed in the form 'input' and the 'response' is also not set.

I am including an image of the modified function, highlighting the change made.

from modular-forms.

Can you check if the problem still occurs in v0.20.0?

from modular-forms.

Can you check if the problem still occurs in v0.20.0?

Hello, excuse my absence.

In the latest version of QwikJS and ModularForms, the same error continues to occur.

from modular-forms.

I would like to know if there is anything I can do to help solve this problem.

from modular-forms.

Maybe this is the problem: vitejs/vite#9528

Does the problem still occur when you run your Qwik application via pnpm preview?

from modular-forms.

Maybe this is the problem: vitejs/vite#9528

Does the problem still occur when you run your Qwik application via pnpm preview?

Hello, yes, in preview mode the error also occurs.

ws [FormError]
    at M2 (file:///Users/caeg.dev/Desktop/duenodirecto/workspace/frontend/server/entry.preview.mjs:294:98288)
    at $e (file:///Users/caeg.dev/Desktop/duenodirecto/workspace/frontend/server/entry.preview.mjs:25:5237)
    at file:///Users/caeg.dev/Desktop/duenodirecto/workspace/frontend/server/entry.preview.mjs:30:2751
    at J (file:///Users/caeg.dev/Desktop/duenodirecto/workspace/frontend/server/entry.preview.mjs:24:1509)
    at file:///Users/caeg.dev/Desktop/duenodirecto/workspace/frontend/server/entry.preview.mjs:30:2618
    at g (file:///Users/caeg.dev/Desktop/duenodirecto/workspace/frontend/server/entry.preview.mjs:30:2878)
    at Object.f2 (file:///Users/caeg.dev/Desktop/duenodirecto/workspace/frontend/server/entry.preview.mjs:294:92884)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.g (file:///Users/caeg.dev/Desktop/duenodirecto/workspace/frontend/server/entry.preview.mjs:30:2855)
    at async file:///Users/caeg.dev/Desktop/duenodirecto/workspace/frontend/server/entry.preview.mjs:16:533 {
  errors: { mobilePhoneNumber: 'Test error.' }
}

from modular-forms.

For what it's worth, this is my "formAction$" that I use to test the error.

export const useAction = formAction$<Register>(() => {
  throw new FormError<Register>({
    mobilePhoneNumber: 'Test error.',
  });
}, zodForm$(register));

from modular-forms.

I just realized that if instead of doing a "throw" you do a "return" the error disappears and everything seems to work correctly.

I used "throw" because the documentation says so.

export const useAction = formAction$<Register>(() => {
  return new FormError<Register>({
    mobilePhoneNumber: 'Test error.',
  });
}, zodForm$(register));

from modular-forms.

This is strange. Since formAction$ uses try/catch, throw should work. I will check this as soon as I find time.

from modular-forms.