mirror of
https://github.com/multica-ai/multica.git
synced 2026-06-16 19:29:26 +02:00
e0b756f515
* refactor(views): replace static timeAgo with shared useTimeAgo hook
The previous timeAgo helper in packages/core/utils.ts hardcoded English
output ("2d ago"), producing "更新于 2d ago" mixed-language strings in
zh locale. Replaced with a localized useTimeAgo() hook in
packages/views/i18n, backed by common.time.{just_now,minutes_ago,
hours_ago,days_ago} translation keys. Migrated all 10 view-side
call sites and removed the static function.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(issues): redesign board card layout
Properties were piling onto the bottom row (assignee + priority badge
+ start date + due date) until it overflowed. Restructured into four
semantic rows:
- Top: priority icon (left, icon-only — color already conveys urgency)
+ identifier; agent activity indicator (right)
- Title
- Chip row: project + labels
- Meta row: assignee (left, avatar + name when only property present;
bare avatar otherwise) + start/due dates + child progress
Long agent/team names truncate cleanly (min-w-0 + max-w-[160px]) and
dates/progress are shrink-0 so they never compress. When the meta row
contains only an assignee, the right side fills with "Updated 2d ago"
to avoid a half-empty row.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
65 lines
2.1 KiB
TypeScript
65 lines
2.1 KiB
TypeScript
export function generateUUID(): string {
|
|
const cryptoObj = globalThis.crypto;
|
|
|
|
if (!cryptoObj?.getRandomValues) {
|
|
throw new Error("Secure UUID generation requires crypto.getRandomValues");
|
|
}
|
|
|
|
const bytes = new Uint8Array(16);
|
|
cryptoObj.getRandomValues(bytes);
|
|
|
|
bytes[6] = ((bytes[6] ?? 0) & 0x0f) | 0x40; // version 4
|
|
bytes[8] = ((bytes[8] ?? 0) & 0x3f) | 0x80; // variant 1
|
|
|
|
const hex = Array.from(bytes, (b) => b.toString(16).padStart(2, "0")).join("");
|
|
|
|
return `${hex.slice(0, 8)}-${hex.slice(8, 12)}-${hex.slice(12, 16)}-${hex.slice(16, 20)}-${hex.slice(20)}`;
|
|
}
|
|
|
|
/**
|
|
* Generate an id that prefers crypto.randomUUID but falls back in non-secure contexts.
|
|
*/
|
|
export function createSafeId(): string {
|
|
const cryptoObj = globalThis.crypto;
|
|
|
|
if (cryptoObj?.randomUUID) {
|
|
try {
|
|
return cryptoObj.randomUUID();
|
|
} catch {
|
|
// Fall through to fallback.
|
|
}
|
|
}
|
|
|
|
return generateUUID();
|
|
}
|
|
|
|
/** Request id helper used for logs/tracing headers. */
|
|
export function createRequestId(length = 8): string {
|
|
return createSafeId().replace(/-/g, "").slice(0, length);
|
|
}
|
|
|
|
/**
|
|
* True when the keyboard event fires while an IME is composing a multi-key
|
|
* input (e.g. Chinese pinyin, Japanese kana). The Enter that commits the
|
|
* composition must NOT trigger submit/send/create handlers.
|
|
*
|
|
* Accepts both React synthetic events and native DOM `KeyboardEvent`s.
|
|
*
|
|
* Why both `isComposing` and `keyCode === 229`:
|
|
* - `isComposing` is the standard signal but Safari clears it on the keydown
|
|
* that ends composition, so a bare check misses the very Enter that submits.
|
|
* - During composition the browser reports `keyCode === 229` regardless of
|
|
* the actual key, which keeps working in Safari's edge case.
|
|
*
|
|
* Always read from `nativeEvent` when present — React's synthetic event is
|
|
* normalized but the native event reflects the browser's real state.
|
|
*/
|
|
export function isImeComposing(event: {
|
|
isComposing?: boolean;
|
|
keyCode?: number;
|
|
nativeEvent?: { isComposing?: boolean; keyCode?: number };
|
|
}): boolean {
|
|
const e = event.nativeEvent ?? event;
|
|
return Boolean(e.isComposing) || e.keyCode === 229;
|
|
}
|