Skip to content

feat(ui): detail consistency — inline errors in editors, unified phrasing (v1.17 G) - #47

Merged
argszero merged 1 commit into
mainfrom
feat/ui-ue-deep-polish-2-consistency
Aug 17, 2026
Merged

argszero merged 1 commit into
mainfrom
feat/ui-ue-deep-polish-2-consistency

Conversation

@argszero

Copy link
Copy Markdown
Owner

Summary

Rant 2026-08-17T16:57:17 (UI/UE 多角度深化优化), item G — 细节一致性 (final item): consistency audit of number/amount formatting, 已用/额度 display, button sizing, and inline-editor error handling.

Audit results (already consistent ✓)

  • All numeric/amount displays go through D.fmt() (thousand separators / 2 decimals) — sidebar balance, stat cards, tables, wallet all uniform;
  • 已用/额度 displayed uniformly; table action buttons all use the small variant (padding:4px 10px;font-size:12px).

Fixes applied

  • Inline editors now use inline errors (align with item E): inlineForm validate failure switched from toast-only to setFieldError (red border + inline text, auto-clear) — covers API Key rename, operator topup, member topup;
  • Removed the 3 stale「(未生效)」suffixes from those messages;
  • Sub-text font-size unified (raise-request email 11px → 12px);
  • Listing toast unit phrasing unified to「点/1M(自动)」.

Acceptance

All 7 items (A–G) of rant 16:57:17 now satisfied — PRs #41–#47, docs v1.17.

Tests

  • node --check on app.js — syntax OK
  • DOM-stub init smoke + field-error smoke (5/5) — all previous behavior intact
  • cargo test — 1 passed
  • cargo fmt --check — clean

@argszero
argszero merged commit 2d492ee into main Aug 17, 2026
1 check passed
argszero added a commit that referenced this pull request Sep 29, 2026
…324)

ui/README.md:90 (the inline-components section) said an inlineForm
`opts.validate` error is surfaced as "toast + 重新聚焦". That was true at
birth (990cd5a, #41) but 2d492ee (#47) changed the code to
`setFieldError(input, err)` and added the `## 一致性约定` section, which
states at line 133 that inline-edit validation goes through
`setFieldError` and explicitly does not use a toast. Only line 90 was
left behind, so the same file contradicted itself and the code.

Fix the wording to match line 133 and the implementation; no behaviour
change, no new i18n keys.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant