Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

[go_router] Platform-adaptive support #99100

Copy link
Copy link
Open
@chunhtai

Description

@chunhtai
Issue body actions

copied from csells/go_router#384

Could you please share an example of how to best deal with the situation where we might have different navigation structures depending on the screen real estate? For example, on smartphones, I would like /users/john to stack 2 screens, one for the list of users and another one for the user details for john. But on a tablet or on the web, I would like to stack just one split screen, with the left part listing users, and the right part showing the user details (nested navigation). It seems to me like it's a very common use case, but I don't see how to do it after reading the doc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projectc: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilityp: go_routerThe go_router packageThe go_router packagepackageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.team-frameworkOwned by Framework teamOwned by Framework team

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.