From f7b3f2de7543e56885fd060348d46263540c333b Mon Sep 17 00:00:00 2001 From: Danila Poyarkov Date: Thu, 30 Apr 2026 16:07:14 +0300 Subject: [PATCH] build(tauri): generate native menu before builds --- AGENTS.md | 2 +- desktop/tauri.conf.json | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 4cafd5ca2..aa1165164 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -306,7 +306,7 @@ Self-review checklist: - Use reka-ui for UI components (Splitter, ContextMenu, DropdownMenu, etc.) - Browser and Tauri menus share `src/app/shell/menu/schema.ts` as the canonical menu model. Do not add menu items directly in `src/components/AppMenu.vue` or `desktop/src/menu.rs`. -- Regenerate the native menu with `bun run generate:tauri-menu` after editing the shared menu schema; `desktop/generated/menu.json` is consumed by the Tauri menu builder. +- Regenerate the native menu with `bun run generate:tauri-menu` after editing the shared menu schema; `desktop/generated/menu.json` is consumed by the Tauri menu builder. Tauri also runs this generator from `desktop/tauri.conf.json` via `beforeDevCommand` and `beforeBuildCommand`. - Every shared menu item with an `id` must be handled by `src/app/shell/menu/use.ts`, an editor command, or explicitly marked browser/native-only in the schema. - Tailwind 4 for styling — no inline CSS, no component-level `