???? ???

Store ?? metadata ?? PageEntry. Use buildPage ? map each page key ? an actual widget.

Serializable state

PageEntry is plain data, so navigation state can be logged, diffed, ? replayed.

Simple resolver

A switch on page.key keeps routing explicit ? reviewable.

One source ? truth

Push ? pop are list operations on _pages, not side effects.

Resolver Pattern

Build by page key ? mutate the page list declaratively.

Page State Rule

Resolver ??

Widget _buildPage(BuildContext context, PageEntry page) {
  switch (page.key) {
    case 'home':
      return HomePage(onGoDetail: _goDetail);
    case 'detail':
      return const DetailPage();
    default:
      return const SizedBox.shrink();
  }
}

void _goDetail() {
  setState(() => _pages = [..._pages, const PageEntry(key: 'detail', name: '/detail')]);
}
Keep Metadata Lean

Avoid placing Widget instances into navigation state ? keep PageEntry as pure metadata ? maintainability.