Relationship required-but-non-localized field validation error when updating global through API

[qbeauperin]

Link to reproduction

https://github.com/qbeauperin/payload/blob/bug/global-localization-required-field/test/localization/config.ts

To Reproduce

• run payload with this config ^
• go to the "Required Relationship Global" global, and add content in English
• run the following code to try and update Spanish through the API:

const response = fetch("http://localhost:3000/api/globals/required-relationship-global?locale=es", { method: 'POST', headers: { 'Content-Type': 'application/json', }, cache: 'no-cache', body: JSON.stringify({text: "some different Spanish text"}) });

• notice how it returns a validation error: The following field is invalid: nonLocalizedRequiredRelationship

Describe the Bug

On the other hand, the exact same config has been duplicated in a collection and work as expected:

• create a new item in the "Required Relationship Collection" collection and add content in English
• run the following code to try and update Spanish through the API:

const response = fetch("http://localhost:3000/api/required-relationship-collection/[yourdocidgoeshere]?locale=es", { method: 'PATCH', headers: { 'Content-Type': 'application/json', }, cache: 'no-cache', body: JSON.stringify({text: "some different Spanish text"}) });

• notice how the update went through properly

Payload Version

1.8.5

[JarrodMFlesch]

Hey @qbeauperin! This has been reported (just linking for clarity, not like you would have known) here. You can install 1.8.4-canary.2 to get the fix, or wait until 1.8.4 is released 👍

[JarrodMFlesch]

Wow. Long day, closed the wrong issue. 😵‍💫

[qbeauperin]

Oh sweet, I'll pull 1.8.4 right now and test it out. Thanks Jarrod! 😄

[qbeauperin]

Issue still occurs in 1.8.4 unfortunately, same repro steps. 😢

Edit: not sure if 1.8.5 was aimed at this, but still occurs unfortunately.

[jacobsfletch]

@qbeauperin wow good catch here. THANK YOU for your detailed report, too. I was able to clone down your repository and easily recreate the bug. I've got the fix in PR #2776 which will go out in the next release.