[Toolset] Locale cannot be saved when Language is empty, although the field is not marked as required

[dariacherepanova]

DIAL chat version

0.1.1

How to reproduce

1. Open the Toolset Editor.
2. Click Add locale.
3. Open the Language dropdown.
4. Try to select a language.
5. Fill in the locale Name and Description if possible.
6. Try to click Save.

Actual result

The locale cannot be saved because the Save button remains disabled.

At the same time:

• the Language field is not marked as required in the UI;
• no validation message indicates that Language must be selected;
• the Language dropdown contains no selectable values and shows No options available.

As a result, the user cannot understand why the locale cannot be saved or how to make the form valid.

Expected result

The form behavior and UI validation should be consistent.

If Language is required:

• the field should be marked as required, e.g. Language *;
• available languages should be present in the dropdown;
• a clear validation message should be shown when no language is selected;
• after selecting a language and filling in the required fields, Save should become enabled.

If Language is optional:

• leaving the field empty should not prevent the locale from being saved.

Confidential information

• I confirm that do not share any confidential information

[PolinaGurinovich97]

The "Add locales" button is gone in #8802 — deliberately. The popup could never be satisfied: the list of content locales is a hardcoded, currently empty array (ADDITIONAL_CONTENT_LOCALE_CODES in apps/chat/src/utils/locale.ts), so the Language dropdown had nothing to offer and Save stayed disabled. With no language to pick, the control now renders nothing at all instead of a dead end. Locales already stored on a deployment are untouched.

It comes back as soon as a language is configurable — making that list runtime-configurable, without an app rebuild, is tracked in #8803.

[dariacherepanova]

Retested in dev, the Add locales element was hidden.