[examples/custom-validation] Set fields to invalid incorrect behaviour

[stefankeil]

Describe the bug
The example suggests to set entry fields to valid or invalid by settingsdk.entry.fields[...].getForLocale(...).setInvalid(true). According to the sdk docs, this actually just works on the field location.

To Reproduce
Steps to reproduce the behavior:

1. use sdk.entry.fields['slug'].getForLocale(sdk.locales.default).setInvalid(true)
   

   apps/examples/custom-validation/src/locations/Field.tsx

   Line 25 in 5f7cd21

   sdk.entry.fields['slug'].getForLocale(sdk.locales.default).setInvalid(true);

Expected behavior
Form Field should get invalid indicator (red bar…)
In the example the slug field should get a red bar

Screenshots

Desktop (please complete the following information):

• OS: Mac OS 13.4.1
• Browser chrome 114.0.5735.198

[whitelisab]

Hi @stefankeil! Thank you for notifying us of this issue. I have logged a ticket with our Developer Experience Team and they will look into it further.

[ghepting]

@stefankeil FYI we're still working on figuring out how to fix this. There's a 3+ year old comment that indicates this has never worked FWIW, but I'm determined to figure out a way 😎

[stefankeil]

Hi @ghepting , thanks for the update and for looking into it :)

[prasannabp33]

Hi @ghepting , Any fix on the issue ?

[bradallenfisher]

i'm too experiencing that custom_validation can indeed notify the user that the field doesn't pass validation, however, it doesn't block/prevent publishing.

Is there a way to utilize setInvalid(true) or setInvalid(false) in order to prevent publishing? they don't do anything for us currently.

Thanks