Skip to content

Commit e4a45ed

Browse files
committed
docs(i18n): validation rule messages follow the edit-beats-catalog rule
Claude-Session: https://claude.ai/code/session_01L6bhgW82YGUW8s8X4Dgiqc Co-authored-by: Claude <noreply@anthropic.com>
1 parent cb1b688 commit e4a45ed

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

‎content/docs/ui/translations.mdx‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -223,6 +223,19 @@ Objects follow the same rule for their `label`, `pluralLabel` and
223223
label an [object extension](/docs/data-modeling/object-extensions) contributes,
224224
for one) is served as written.
225225

226+
An object's validation rule messages follow it too, on both places a reader
227+
sees them: the error a rejected write returns, and the rule served with the
228+
object (`/meta`, and the forms built from it). The rule's `message` is compared
229+
with the message of the rule of the same `name` in the owning package's
230+
declaration, a `conditional` rule's `then` / `otherwise` branch by its own name.
231+
An organization that overlays a packaged object and rewords a rule's message,
232+
keeping its name, gets that sentence as written in every locale; the rules it
233+
left alone are still translated, and both places always show the same sentence.
234+
Unlike a widget or a bulk action, a rule the owning package does not declare
235+
(one an object extension adds, or one the organization added) is **still
236+
translated** under its own name, `objects.<name>._validations.<rule>.message`:
237+
there is no shipped message for it to differ from.
238+
226239
## Organizing the files
227240

228241
How you lay out translation source files is an authoring convention — your

0 commit comments

Comments
 (0)