build method

@override Widget build(BuildContext context, WidgetRef ref)

Describes the part of the user interface represented by this widget.

The framework calls this method when this widget is inserted into the tree in a given BuildContext and when the dependencies of this widget change (e.g., an InheritedWidget referenced by this widget changes). This method can potentially be called in every frame and should not have any side effects beyond building a widget.

The framework replaces the subtree below this widget with the widget returned by this method, either by updating the existing subtree or by removing the subtree and inflating a new subtree, depending on whether the widget returned by this method can update the root of the existing subtree, as determined by calling Widget.canUpdate.

Typically implementations return a newly created constellation of widgets that are configured with information from this widget's constructor and from the given BuildContext.

The given BuildContext contains information about the location in the tree at which this widget is being built. For example, the context provides the set of inherited widgets for this location in the tree. A given widget might be built with multiple different BuildContext arguments over time if the widget is moved around the tree or if the widget is inserted into the tree in multiple places at once.

The implementation of this method must only depend on:

• the fields of the widget, which themselves must not change over time, and
• any ambient state obtained from the context using BuildContext.dependOnInheritedWidgetOfExactType.

If a widget's build method is to depend on anything else, use a StatefulWidget instead.

See also:

• StatelessWidget, which contains the discussion on performance considerations.

Implementation

@override
Widget build(BuildContext context, WidgetRef ref) {
  final l10n = WalletLocalizations.of(context);
  // The deposit gate's single reader: a WalletSession is exposed ONLY in
  // OnboardingActive (walletSessionProvider derives that). When present — the
  // active path, and the path the screen tests inject directly — render the
  // live wallet; otherwise render the matching onboarding phase. A wallet is
  // never shown as deposit-ready before its backup is confirmed-and-persisted.
  final session = ref.watch(walletSessionProvider);
  // Host seam: the Settings entry points (the seam keeps its historical
  // "appearance" name) render only when the host wired a destination (the
  // package has no settings surface of its own).
  final appearanceRoute = ref.watch(walletAppearanceRoutePathProvider);
  // The ACTIVE wallet is a tab root in the refreshed design (FR-49 S12, C1):
  // a large title that scrolls with the content, drawn by _WalletActive's
  // own header — no AppBar. The status-bar icon brightness the AppBar used to
  // set is applied here instead.
  if (session != null) {
    return Scaffold(
      body: AnnotatedRegion<SystemUiOverlayStyle>(
        value: overlayStyleFor(WalletColors.of(context)),
        child: const SafeArea(child: _WalletActive()),
      ),
    );
  }
  // Pre-Active (onboarding; `session` is null here): the plain title and a
  // bare Settings action, so the host's settings stay reachable
  // before a wallet exists (when the wallet is the host's home there is no
  // separate settings surface). The active wallet's header — the watch-only
  // chip, the eye and the overflow menu — is `_WalletHeader` above.
  return Scaffold(
    appBar: AppBar(
      title: Text(l10n.walletTitle),
      actions: [
        if (appearanceRoute != null)
          IconButton(
            tooltip: l10n.walletAppearanceMenuItem,
            icon: const WalletIcon(WalletGlyph.appearance),
            onPressed: () => context.push(appearanceRoute),
          ),
      ],
    ),
    body: SafeArea(child: _onboarding(ref, l10n)),
  );
}