Scope

What's changed:

• In validation-errors component, prop values were passed directly to useValidationErrorDetails using toRef.
• passing toRef(props.validationErrors) doesn’t keep the prop value properly synchronised.
• updated the component to pass prop values using toRef's getter syntax to fix discrepancies.

Potential Risks / Drawbacks

• None that I'm aware of.

Tested Scenarios

• All 4 scenarios reported in Error messages do not update properly when creating Items #26227 were tested. Reposted below:
• Attempt to submit an empty form. Required field validation messages will display as expected.
• Enter a value for Name and submit again. Required field validation messages will still display for both Name and Color, even though Name now has a value.
• Fill in the required fields and enter invalid values for Must Be Yes and Must Be No. Here, required field validation message go away and the custom validation messages are displayed.
• Clear out the Name field and hit submit again. The required field validation message for Name will not be displayed, only the already existing custom validation messages.

Review Notes

• note this toRef(props, 'validationErrors') also works.
• toRef's doc recommends using the getter syntax for Vue version 3.3+ so I went with that.

Questions

• This wasn't raised in the issue but needs clarification:

In a case where you have both required and non-required fields in a form, and you submit the form with any of the required fields empty and non-required fields filled with invalid values. The validation errors appear only for the required values. Errors for non-required fields appear only when the required fields are also filled and submitted.

From my investigation, this is because required fields are validated immediately on the client side, but for non-required fields, the request goes to the server first, and if any, the validation errors are returned. This works fine, except that the user would not see all errors at once in a case like this.

Note, this PR does not address this issue. If this is how it is expected to work, then this PR addresses all the bugs raised in the issue.

Checklist

• Added or updated tests
• Documentation PR created here or not required
• OpenAPI package PR created here or not required

Fixes #26227