17911 translations should affect the required validation rule #17925
+23
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added a new "Validation" translation category with a required‑field message, and wired form validation to use it so the required text can be customised via the translations feature. The required rule now pulls validation.required from translations, falling back to the previous "Required" message when no override is set.
Addresses
Screenshots
Launchcontrol
Adds a new Validation section for translations that includes a message for required fields. The form now uses this message when showing "required" errors, so the wording can be changed through translations. If no custom message is provided, it will still show the original “Required” text as a fallback.
Summary by cubic
Adds a new Validation translation group and uses it for required-field errors in forms so teams can localize or customize the message. If no translation is set, it falls back to "Required".
New Features
Migration
Written for commit b6b7323. Summary will update on new commits.