Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make wording in nested nav recipe device-agnostic. #11775

Merged
merged 2 commits into from
Mar 5, 2025
+12 −7
Merged

Make wording in nested nav recipe device-agnostic. #11775

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b2517d6
Make wording in nested nav recipe device-agnostic.
antfitch Mar 4, 2025
2de6d69
Merge branch 'main' into ios_nested_nav
antfitch Mar 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion site-shared
Open in desktop
Submodule site-shared updated 1 files
+10 −10 .github/workflows/dart.yml
17 changes: 11 additions & 6 deletions src/content/cookbook/effects/nested-nav.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,13 +19,18 @@ be better handled nested within another widget.

Consider an Internet of Things (IoT) setup flow for a wireless
light bulb that you control with your app.
This setup flow consists of 4 pages:
find nearby bulbs, select the bulb that you want to add,
add the bulb, and then complete the setup.
This setup flow consists of four pages:

* `find_devices` page: Find nearby bulbs.
* `select_device` page: Select the bulb that you want to
add.
* `connecting` page: Add the bulb.
* `finished` page: Complete the setup.

You could orchestrate this behavior from your top-level
`Navigator` widget. However, it makes more sense to define a second,
nested `Navigator` widget within your `SetupFlow` widget,
and let the nested `Navigator` take ownership over the 4 pages
and let the nested `Navigator` take ownership over the four pages
in the setup flow. This delegation of navigation facilitates
greater local control, which is
generally preferable when developing software.
Expand Down Expand Up @@ -160,7 +165,7 @@ want to exit the setup flow.

Prompt the user to confirm exiting the setup flow,
and ensure that the prompt appears when the user
presses the hardware back button on Android.
presses the hardware back button on their device.

<?code-excerpt "lib/prompt_user.dart (PromptUser)"?>
```dart
Expand Down Expand Up @@ -232,7 +237,7 @@ PreferredSizeWidget _buildFlowAppBar() {
```

When the user taps the back arrow in the app bar,
or presses the back button on Android,
or presses the back button on their device,
an alert dialog pops up to confirm that the
user wants to leave the setup flow.
If the user presses **Leave**, then the setup flow pops itself
Expand Down