[flutter_adaptive_scaffold] - Display an AppBar on bigger screen than mobile

[wer-mathurin]

Is there an existing issue for this?

• I have searched the existing issues
• I have read the guide to filing a bug

Use case

This can be common to display on Desktop and table an AppBar to show widget (eg. Search field) like in Gmail.

Today this is impossible because the logic prevent that in the AdaptiveScaffold

appBar: widget.drawerBreakpoint.isActive(context) && widget.useDrawer
        ? widget.appBar ?? AppBar()
        : null,

Proposal

This can be fixed by adding a new property to the Widget => Breakpoint? appBarBreakpoint
This way we are not breaking the API and can display an AppBar is needed on defined breakpoints. It also not relying on the useDrawer flag!

 appBar: widget.drawerBreakpoint.isActive(context) && widget.useDrawer ||
              (widget.appBarBreakpoint?.isActive(context) ?? false)
          ? widget.appBar ?? AppBar()
          : null,

This way we can use the AdaptiveScaffold

   final double leadingWidth =
            Breakpoints.large.isActive(context) ? 192 : 72;

        return Theme(
          data: Theme.of(context).copyWith(
              appBarTheme: AppBarTheme.of(context).copyWith(
                  backgroundColor: Colors.grey.shade200,
                  iconTheme:
                      IconTheme.of(context).copyWith(color: Colors.grey))),
          child: AdaptiveScaffold(
            appBar: MyCustomAppBar(leadingWidth: leadingWidth),
            appBarBreakpoint: Breakpoints.smallAndUp,
...

With this setup we can achieve this in
mobile

tablet

desktop

[wer-mathurin]

@darshankawar Just to let you know I did a PR for this:
flutter/packages#4434

Just need someone to review it.

[flutter-triage-bot]

The fyi-ecosystem label is redundant with the team-ecosystem label.

[wer-mathurin]

@stuartmorgan the PR have been merged and plugin have been published. You can close this issue !

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.