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.

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

[router] add pop/popToTop/canPop #26711

Merged
merged 7 commits into from
Feb 12, 2024
Merged

[router] add pop/popToTop/canPop #26711

merged 7 commits into from
Feb 12, 2024

Conversation

marklawlor
Copy link
Contributor

Why

Add pop/popToTop/canTop to the router apis (both hooks and imperative).

How

Test Plan

Checklist

@expo-bot expo-bot added the bot: suggestions ExpoBot has some suggestions label Jan 26, 2024
@expo-bot expo-bot added bot: passed checks ExpoBot has nothing to complain about and removed bot: suggestions ExpoBot has some suggestions labels Jan 29, 2024

### `pop` action

Go back in the stack by the number of screens specified in the `count` parameter. If no `count` is specified, then it will go back to the previous screen in the stack.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be clear how this differs from "goBack"

);
}

```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a goBack vs pop example section in here.

@marklawlor
Copy link
Contributor Author

Rename to dismiss

@marklawlor marklawlor force-pushed the marklawlor/router/pushToTop branch 2 times, most recently from 789e4dd to f2e28ee Compare February 8, 2024 23:29
@marklawlor marklawlor merged commit ea0cf58 into main Feb 12, 2024
13 checks passed
@marklawlor marklawlor deleted the marklawlor/router/pushToTop branch February 12, 2024 07:49
marklawlor added a commit that referenced this pull request Feb 28, 2024
# Why

Add `pop`/`popToTop`/`canTop` to the router apis (both hooks and
imperative).

# How

<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan

<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
Co-authored-by: Aman Mittal <amandeepmittal@live.com>
@brentvatne brentvatne added the published Changes from the PR have been published to npm label Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot: fingerprint compatible bot: passed checks ExpoBot has nothing to complain about published Changes from the PR have been published to npm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants