页面组件文案没有翻译位:12 处用户可见字符串(首页占 10)在 zh/ja/es 下只能是英文,而 dashboards.widgets 有同形的翻译面 #1004

Activity

1. yinlianghui

   added

   metadataDeclarative metadata — schema, security posture, UI surfacesDeclarative metadata — schema, security posture, UI surfaces

   upstream:objectstackBlocked on / caused by the ObjectStack platform — tracked upstreamBlocked on / caused by the ObjectStack platform — tracked upstream

   pm:blocked

   on Aug 6, 2026
2. yinlianghui commented on Aug 6, 2026

   

   yinlianghui

   on Aug 6, 2026 – with Claude

   ContributorAuthor

   More actions

   上游镜像已建:objectstack-ai/objectstack#6080(Blocked-by)

   按上游协议处理:本单症结在 @objectstack/spec 的翻译契约(pages 为 .strict() 四键、无组件文案面),不是 hotcrm 侧可修的——语言包写不进(strict 拒收)、运行时无处读,应用侧任何"修法"都是平台 workaround,⛔ 不做。

   • 镜像单含完整证据:契约形状、title/subtitle 归 page:header 的语义口径、与 dashboards.widgets 的不对称对照、12 处 dist 实测面,并给了建议方向(pages.components 面与 widgets 对齐);
   • 本单标 pm:blocked + upstream:objectstack,待上游补面后回来消化(届时语言包补 zh/ja/es 三语、test/i18n-references.test.ts 扩面覆盖组件键);
   • 同族 closing_this_quarter 的切换器页签标题写作 "Closing Soon" —— 与 label / 四个语言包的第四个拼法,且 tabs[].label 没有翻译位 #760(tabs[].label 无翻译位)维持原状,镜像单里已互相关联——上游若补面,两条一起解锁。

   ---

   Generated by Claude Code
3. huangyiirene commented on Aug 11, 2026

   

   huangyiirene

   on Aug 11, 2026 – with Claude

   Collaborator

   More actions

   Re-measured on @objectstack/* 17.0.0-rc.6 during the rc.5 → rc.6 upgrade (#1059, PR #1066). The asymmetry this card identified is closed upstream — option 1 in the disposition list ("上游补面") is what shipped.

   pages in the translation contract is no longer four keys. It now carries a components face, keyed by component id, exactly parallel to dashboards.widgets:

   pages: Record(name, {
     label?, description?, title?, subtitle?,
     components: Record(id, {
       title?, description?, label?, placeholder?, emptyText?, submitLabel?
     })   // strict
   })

   The face is wider than this card asked for — beyond title / description / label it adds placeholder, emptyText and submitLabel — so it covers component copy this card did not enumerate. (settings and metadataForms gained comparable faces in the same contract.)

   So all 12 strings listed here now have a translation slot: the 10 on sales_home_page (quick_create.title, the four KPI labels, ai_briefing.title / .description, etc.), lead_detail_page.related_tasks.title, and utility_bar_page.quick_notes.title. A zh-CN user's landing page no longer has to be two languages on one screen.

   Not done here: this PR is the dependency bump only. Actually populating components across the four locale bundles — and extending test/i18n-references.test.ts to walk the new face so the coverage guard can finally see page component copy — is app-side work with a real review surface. Worth reopening this card's scope as that follow-up, or filing it fresh.

   Scope note: static read of the shipped @objectstack/spec translation schema. Not verified in a browser that the console actually resolves pages.<name>.components.<id>.title at render time — the point #1004's option 3 raised, and still the right thing to check before writing 12 strings × 4 locales.

   ---

   Generated by Claude Code
4. hotlong commented on Aug 14, 2026

   

   hotlong

   on Aug 14, 2026 – with Claude

   Contributor

   More actions

   Transfer sweep (#1156, part 1) — outcome 2: the fix lands in hotcrm. Relabelled and kept here.

   The outcome test that was applied

   Where would the fix land today? The upstream:objectstack label was correct when applied on 2026-08-06 — the contract genuinely had no key to write into. It is stale now.

   Verdict: the upstream gap this card identified is closed; what is left is app-side

   Platform half — shipped. The mirror objectstack#6080 ("翻译契约 pages 无组件文案面") is closed / completed, via merged PR objectstack#6466 ("feat(spec): translatable page component copy"). Verified upstream directly, not inferred from the on-card note.

   The contract's pages face is no longer four strict keys. It now carries a component face keyed by component id, parallel to dashboards.widgets — which is precisely the asymmetry argument this card made, and option 1 of its own disposition list (「上游补面」) is what shipped. The delivered face is wider than this card asked for: beyond title / description / label it also carries placeholder, emptyText and submitLabel.

   So all 12 strings enumerated in the body now have a translation slot — the 10 on sales_home_page, lead_detail_page.related_tasks.title, and utility_bar_page.quick_notes.title. The value chain this card described (literals in *.page.ts straight through to dist/objectstack.json, unwritable because .strict() rejects the key) no longer holds.

   App half — outstanding, and it is real work with a review surface. Populate the component copy across the four locale bundles, and extend test/i18n-references.test.ts to walk the new face so the coverage guard can finally see page component copy — today it cannot, which is how this gap stayed invisible until #1002 tripped over it. That is app-side work in this repo, so there is no platform need left to route anywhere.

   Actions taken on this card

   • upstream:objectstack — removed. The upstream ask was made, accepted and shipped.
   • pm:blocked — removed. The blocking condition (no key in the contract) is gone.
   • prio:p2 added. This card carried no priority grade at all. P2 (triaged backlog, no near-term schedule) is the honest grade: the user-visible symptom is real — a zh-CN user's landing page is two languages on one screen, on an isDefault: true page shipped to sales_rep / sales_manager — but it is copy, not function, and nothing is broken.
   • metadata — kept.
   • Left open. Not one of the 12 strings has been written.

   ⚠️ Carried forward: this card's option 3 is still unanswered, and it is the right first step

   The body's option 3 asked whether the console actually renders these literals — i.e. whether it resolves pages.[ name ].components.[ id ].title at render time, or only accepts the key in the schema. Everything established above is a static read of the shipped contract. Nobody has confirmed the render-time resolution in a browser.

   That matters practically: writing 12 strings × 3 locales against a key the console does not read would produce a silently ineffective change that still passes every guard. Check the render path first, then write the bundles.

   ⛔ And note what that check is not grounds for. If the console turns out not to resolve the key, that is a new finding against the console at that point — file it fresh, in objectui, with the measurement. It is not a reason to keep this card labelled upstream:objectstack today on a defect nobody has observed.

   What was NOT done here

   No app boot, no browser check, no code, no locale bundles touched. This sweep is routing and bookkeeping only. The upstream half was verified by reading objectstack#6080's state and its merged closing PR; the render-time question above is exactly the part that remains unmeasured, and it is named rather than assumed either way.

   Related, unchanged

   #760 (tabs[].label has no translation slot) is the sibling case and was cross-linked from the upstream mirror on the expectation that both unlock together. This sweep did not touch it — it is not in part 1's six cards. Whoever picks up #1004 should re-check whether the shipped face covers #760 as well; if it does, #760 needs the same relabelling this card just got.

   Authority

   • [Transfer sweep] Move all 22 platform-defect cards to the repo the fix lands in, and close them here with a pointer #1156 (transfer sweep), part 1.
   • Maintainer ruling, 2026-08-14 — verbatim, untranslated:

   hotcrm 席位的原则是用平台的能力做元数据应用的开发，平台的需求应该转给平台

   This card is the ruling working as intended: the platform need was routed to the platform, the platform built the capability, and what returns is an app using it. The companion disposition 「关掉,只留指向镜像的指针」 does not apply — the mirror is already closed, and pointing a reader at a closed card would hide the app-side work that is the only thing left.

   ---

   Generated by Claude Code

   ---

   Generated by Claude Code
5. hotlong

   added

   prio:p2

   and removed

   upstream:objectstackBlocked on / caused by the ObjectStack platform — tracked upstreamBlocked on / caused by the ObjectStack platform — tracked upstream

   pm:blocked

   on Aug 14, 2026
6. hotlong

   added

   pm:blocked

   on Aug 25, 2026
7. hotlong commented on Aug 25, 2026

   

   hotlong

   on Aug 25, 2026 – with Claude

   Contributor

   More actions

   Triage (代扫, vacancy clause) → pm:blocked, Blocked-by: objectstack-ai/objectstack#12231 (filed by this seat just now).

   Filed 2026-08-06 with metadata + prio:p2 and no pm-state — nineteen days invisible. Vacancy clause: triage actions only.

   The card asked triage to choose among three routes. Two of them are already decided by the charter.

   • Route 1, upstream — the charter's own instruction: 「平台相关的功能应该在平台中实现」. A missing face in the translation contract is as platform-side as it gets. Taken, filed as objectstack#12231 with the asymmetry, the 12-string surface and the boundary of what is measured.
   • Route 2, app-side workaround — ⛔ not available in this lane. The charter forbids it in terms: 「永不在 hotcrm 内绕行 —— 绕行把平台缺口藏进样板,展品从此示范错误写法」. Moving copy onto whatever surface happens to have a slot, or writing an explicit exemption into a guard, is precisely hiding a platform gap inside the exemplar. Recording that here so the next reader does not re-open it as an option.
   • Route 3, measure first — legitimate, and it is a question about impact, not existence, so it does not gate the filing. Carried into the upstream card as an explicit unestablished claim rather than dropped.

   That leaves nothing this repo can do until the slot exists, which is the definition of pm:blocked.

   ⚠️ The part of this card that is inference, kept labelled as inference

   What is measured and renderer-independent: the key does not exist. pages is .strict() with four keys, so a locale pack is refused permission to carry component copy — this is not an English fallback, it is a closed door.

   What is inferred: that all 12 strings reach the screen as written. The sibling case #760 was filed on comparable static evidence about list.tabs[].label and was closed this week as premise-false — the switcher rendered a different string entirely and there was no user-visible symptom at all. Same family, same kind of static argument, opposite outcome on measurement.

   So the "同一屏两种语言" figure is the strong claim on this card and the least verified one. It is stated as such in objectstack#12231 rather than carried across as fact. ⛔ Whoever eventually implements this should not quote the 12-string count forward as a verified impact figure without a browser read.

   prio:p2 retained.

   ---

   Generated by Claude Code
8. claude

   added

   priority:p2Medium: important, M3Medium: important, M3

   and removed

   prio:p2

   on Sep 9, 2026