Required Fields Per Locale

[jessrynkar]

Description

Users have reported that when a field is marked as required, they expect validation to run across all locales — meaning that saving or publishing in one locale should fail if the required field is missing in another locale.

Currently this is not enforced. Validation only runs against the currently active locale. While this behavior avoids blocking saves, it creates confusion and can lead to incomplete data being marked as “published.”

If we were to enforce required fields across all locales right now, the workflow would break down:

• Users can only edit one locale at a time in the admin panel.
• This would force them to save draft data in every locale before they could publish.
• If drafts are not enabled, they would not be able to save at all, since they could never satisfy validation for fields in other locales.

Because of this, we’ve decided not to enforce required fields across locales until multi-locale editing is available. With multi-locale editing, users will be able to fill in missing values for multiple locales in a single view, making strict validation feasible and user-friendly.

Proposal

Since this changes the expected behavior of required, we’d like to introduce a new configuration option that gives developers control over which locales a field should be required in.

Possible approaches:

{
  name: "someField",
  type: "text",
  localized: {
    required: ["en", "de"], // required only in 'en' and 'de'
  }
}

{
  name: "someField",
  type: "text",
  required: {
    en: true,
    es: false,
  }
}

Details

• Required fields should be enforceable across locales.
• Fields should support a config that makes them required only for specific locales.
• Locales marked as non-required should continue to fall back to their defined fallback locale(s).

ETA

TBD

Background

Original discussion here.