Skip to content

Commit cefd0de

Browse files
committed
chore(changeset): spec patch for the navigation label resolution order
Claude-Session: https://claude.ai/code/session_01Sfe5YjBLwB9J3y8fvm2xq1 Co-authored-by: Claude <noreply@anthropic.com>
1 parent c91894a commit cefd0de

1 file changed

Lines changed: 18 additions & 0 deletions

File tree

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
'@objectstack/spec': patch
3+
---
4+
5+
docs(spec): a navigation entry's `label` describe states the one order the label resolves in
6+
7+
Clause-②: no
8+
9+
The `label` of a navigation entry (`BaseNavItemSchema`) said a present label "renders
10+
verbatim and is never overwritten", which, read literally, forbids the id-keyed localization
11+
`translateApp` already performs at the `/meta` boundary. Its describe and JSDoc now state one
12+
order: the bundle entry `apps.<app>.navigation.<id>.label` for the active locale chain, keyed
13+
by the entry's `id` and applied by `translateApp` over the app's `navigation` tree (not
14+
`areas`); else a present label as authored — its inline locale map's value for that locale,
15+
else its text; else, when absent, the current label of what the entry opens, at render time,
16+
localized by the target's own translation. A present label is never replaced by its target's
17+
label and never translated by matching its text. No accepted shape changes: `label` stays an
18+
optional `I18nLabel`.

0 commit comments

Comments
 (0)