Summary

Fixes #15828

When using locale: 'all' with a required localized text field, the text validator incorrectly rejects the value. This happens because:

1. With locale: 'all', the value passed to the validator is an object like {en: "Hello", es: "World"} (locale unflattening via mergeLocaleActions happens after validation in promise.ts)
2. The old condition !(typeof value === 'string' || Array.isArray(value)) evaluates to true for objects, triggering the required error
3. The textarea validator already handles this correctly by using !value (objects are truthy)

Fix

Changed the text validator's required check from:

if (!(typeof value === 'string' || Array.isArray(value)) || value?.length === 0)

to:

if (!value || ((typeof value === 'string' || Array.isArray(value)) && value.length === 0))

This aligns with the textarea validator's approach:

• !value catches null, undefined, and empty string ""
• The second clause catches empty arrays [] (truthy but length 0)
• Localized objects like {en: "Hello"} pass because !obj is false

Changes

• packages/payload/src/fields/validations.ts — 1-line fix to the required check condition
• packages/payload/src/fields/validations.spec.ts — 3 unit tests (localized object accepted, null rejected, empty string rejected)
• test/fields/collections/Text/index.ts — Added localizedRequiredText test field
• test/fields/int.spec.ts — Integration test verifying locale: 'all' with required localized text

Test plan

• Unit tests: 88/88 passed (85 existing + 3 new)
• Integration tests (SQLite): 154/154 passed
• CI passes on all database adapters