You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 4, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 4, 2026. It is now read-only.
Studio: offer to scaffold navigation from existing objects when creating an app #2262
Mirror of framework#2615 (P2 — highest-ROI item there), found by the Studio package-create UX dogfood (framework#2609). Reproduced against the pinned console build 7782698.
What happens
"Create app" produces an app with zero nav items. The object the user just built isn't offered anywhere; they must discover Interfaces → Edit → Add nav item → set Label → Link to object. In the dogfood run this manual wiring was the single biggest discontinuity in an otherwise smooth create-package → publish loop.
Expected
The create-app popover gains an "Add existing objects as menu items" option (checked by default when the package has objects). Each generated nav item is pre-labeled with the object's label and linked to its record list — exactly what the manual flow produces today.
Notes
Small surface: the nav editor and object→nav-item binding already exist; this only pre-populates them at app creation.
Activity
Merge origin/main: adopt upstream #2263/#2271, keep nav scaffold + i1…