Form validation errors not displayed on Register.vue

[zhongruige]

Jetstream Version

4.0

Jetstream Stack

Inertia

Laravel Version

10.29.0

PHP Version

8.2.11

Database Driver & Version

No response

Description

Hi there--

I just did a fresh install of the latest Jetstream and Laravel using the inertia stack. I noticed that the error messages aren't showing on the register form as they used to on previous versions. I was able to fix this using defineProps({ errors: Object }) and update the fields from form.errors to errors but wanted to note this issue here, too. It seems like the email field error returns as expected, just not the password errors.

Steps To Reproduce

On a fresh install (using the Inertia stack), register a user with any password that doesn't meet the requirements. Click to register and note that the error doesn't show:

To verify the errors are being caught as expected and just not displayed, add defineProps({ errors: Object }) and update the input errors from form.errors to errors. Try and register again and note that the password error is now showing:

[crynobone]

The https://inertiajs.com/forms#form-helper documentation seems to suggest current usage is already correct.

[jessarcher]

This issue exists on Breeze as well.

It only happens with the latest version of Inertia because of this change and because we're calling form.reset to clear the password fields:

    form.post(route('register'), {
        onFinish: () => form.reset('password', 'password_confirmation'),
    });

I will chat with @reinink to confirm whether we should fix it in Inertia or Jetstream and Breeze.

[jessarcher]

I've reverted the change in Inertia and released v1.0.14.

[zhongruige]

I've reverted the change in Inertia and released v1.0.14.

Thanks so much for the quick turn around on this @jessarcher! Appreciate it. Fix worked great for me 🙌

[JackHardy]

@jessarcher I am currently having this same issue using inertiajs/ineria-laravel and laravel-precognition-vue-inertia. Should the PR above have rectified this too? (or is this a me issue)

[jessarcher]

@JackHardy It should have, yeah. Are you able to replicate the issue on a minimal clean install?

[JackHardy]

@jessarcher False alarm; apologies.