zhangwenjian b3a740ab2a feat✨(example): register the order routes, migration and menu seed ...

Registration goes through core's package-level facades: SetAppRouters for
the routes, migration.ForApp for the schema, and seed.MenuSpec/ApiSpec
for the menu rows - none of which requires importing the host.

The menu component is spelled apps/order/order/index. The frontend tells
a packaged view from a built-in one by that first segment alone, and
getting it wrong is silent: the page falls back to the not-installed
placeholder while the console names a src/views path that was never going
to exist. The tests assert that prefix, that every Parent reference
closes, and that every ApiCode resolves - the three ways a menu graph is
wrong without anything saying so.

Claude-Session: https://claude.ai/code/session_01HPTAw8b8tAdFNFn8rKdPYx

2026-09-05 10:27:41 +08:00

..

router_test.go

feat✨(example): register the order routes, migration and menu seed

2026-09-05 10:27:41 +08:00

router.go

feat✨(example): register the order routes, migration and menu seed

2026-09-05 10:27:41 +08:00