-
Couldn't load subscription status.
- Fork 390
style: update Vue node designs to use semantic tokens #6304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🎨 Storybook Build Status✅ Build completed successfully! ⏰ Completed at: 10/27/2025, 03:38:53 PM UTC 🔗 Links🎉 Your Storybook is ready for review! |
Bundle Size ReportSummary
Category Glance Per-category breakdownApp Entry Points — 3.29 MB (baseline 3.3 MB) • 🟢 -83 BMain entry bundles and manifests
Status: 2 added / 2 removed Graph Workspace — 721 kB (baseline 721 kB) • ⚪ 0 BGraph editor runtime, canvas, workflow orchestration
Status: 1 added / 1 removed Views & Navigation — 8.15 kB (baseline 8.15 kB) • ⚪ 0 BTop-level views, pages, and routed surfaces
Status: 1 added / 1 removed Panels & Settings — 294 kB (baseline 294 kB) • ⚪ 0 BConfiguration panels, inspectors, and settings screens
Status: 6 added / 6 removed UI Components — 12.3 kB (baseline 12.3 kB) • ⚪ 0 BReusable component library chunks
Status: 1 added / 1 removed Data & Services — 10 kB (baseline 10 kB) • ⚪ 0 BStores, services, APIs, and repositories
Status: 1 added / 1 removed Utilities & Hooks — 1.07 kB (baseline 1.07 kB) • ⚪ 0 BHelpers, composables, and utility bundles
Vendor & Third-Party — 5.36 MB (baseline 5.36 MB) • ⚪ 0 BExternal libraries and shared vendor chunks
Other — 2.55 MB (baseline 2.55 MB) • ⚪ 0 BBundles that do not match a named category
|
…6320) ## Summary Fixes `trackTemplate` calls to use raw template ID instead of translated workflow name for analytics tracking. ## Problem When users load templates with non-English locale, the `workflow_name` field was being tracked in their language (e.g., "默认工作流" for Chinese users) instead of English. This makes statistical analysis difficult. ## Changes - Updated both `trackTemplate` calls in `useTemplateWorkflows.ts` to use raw `id` instead of translated `workflowName` - The translated name is still used for display purposes in `loadGraphData` **Before:** ```typescript useTelemetry()?.trackTemplate({ workflow_name: workflowName, // Could be "默认工作流" template_source: sourceModule }) ``` **After:** ```typescript useTelemetry()?.trackTemplate({ workflow_name: id, // Always "default" template_source: sourceModule }) ``` ## Testing - [x] Type checking passes - [x] Verified translated names still used for display ## Related Part of comprehensive i18n audit for telemetry tracking. Related to template metadata English tracking in PR #6304. ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-6320-bugfix-use-raw-template-ID-for-workflow_name-in-telemetry-tracking-2996d73d365081d8aef3fa2529a10247) by [Unito](https://www.unito.io)
…6320) ## Summary Fixes `trackTemplate` calls to use raw template ID instead of translated workflow name for analytics tracking. ## Problem When users load templates with non-English locale, the `workflow_name` field was being tracked in their language (e.g., "默认工作流" for Chinese users) instead of English. This makes statistical analysis difficult. ## Changes - Updated both `trackTemplate` calls in `useTemplateWorkflows.ts` to use raw `id` instead of translated `workflowName` - The translated name is still used for display purposes in `loadGraphData` **Before:** ```typescript useTelemetry()?.trackTemplate({ workflow_name: workflowName, // Could be "默认工作流" template_source: sourceModule }) ``` **After:** ```typescript useTelemetry()?.trackTemplate({ workflow_name: id, // Always "default" template_source: sourceModule }) ``` ## Testing - [x] Type checking passes - [x] Verified translated names still used for display ## Related Part of comprehensive i18n audit for telemetry tracking. Related to template metadata English tracking in PR #6304. ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-6320-bugfix-use-raw-template-ID-for-workflow_name-in-telemetry-tracking-2996d73d365081d8aef3fa2529a10247) by [Unito](https://www.unito.io)
Complete the semantic token migration by updating final hard-coded colors in widget components to use design system tokens: - MultiSelect.vue: text-neutral-400 → text-secondary - Ensure consistent text-primary/text-secondary usage across all widgets - Remove hard-coded zinc, neutral, and other color values 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Complete the semantic token migration by updating final hard-coded colors in widget components to use design system tokens: - FormSelectButton.vue: use text-primary/text-secondary consistently - FormDropdownMenuFilter.vue: use text-secondary for default text - FormDropdownMenuItem.vue: use text-secondary for metadata - AudioPreviewPlayer.vue: use text-secondary for icons - Remove hard-coded zinc, neutral, and other color values from vueNodes 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
033c50e to
20015cc
Compare
🎨 Storybook Build Status✅ Build completed successfully! ⏰ Completed at: 10/27/2025, 05:15:19 AM UTC 🔗 Links🎉 Your Storybook is ready for review! |
Update test expectations to use semantic color tokens instead of hard-coded classes: - bg-white → bg-interface-menu-component-surface-selected - text-neutral-900 → text-primary/text-secondary - hover:bg-zinc-200/50 → hover:bg-interface-menu-component-surface-hovered
Update test expectations to use semantic color tokens instead of hard-coded classes: - bg-white → bg-interface-menu-component-surface-selected (25 instances) - text-neutral-900 → text-primary (3 instances) - hover:bg-zinc-200/50 → hover:bg-interface-menu-component-surface-hovered (2 instances)
|
LGTM |
Restore the semantic token migration for MultiSelect.vue: - text-neutral-400 dark-theme:text-zinc-500 → text-secondary This completes the semantic token migration across all components.
…elect.vue - Disable eslint-plugin-tailwindcss due to TailwindCSS v4 incompatibility - Revert MultiSelect.vue changes as they were not part of vueNodes scope The eslint-plugin-tailwindcss v4.0.0-beta.0 is incompatible with TailwindCSS v4.1.12 as it tries to load v3 file structure that no longer exists.
…n knip Due to TailwindCSS v4 compatibility issues with eslint-plugin-tailwindcss v4.0.0-beta.0, we temporarily disabled the plugin in eslint.config.ts. This causes knip to detect these dependencies as unused, so we add them to ignoreDependencies until the compatibility issue is resolved. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>

Summary
Use semantic tokens instead of colors
┆Issue is synchronized with this Notion page by Unito