Repository navigation
Revert "Return to the intent list from work email Back after a refresh" - #103646
carlosmiceli wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c4ae144ed5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <OnboardingHeader | ||
| shouldShowBackButton={isJoiningCompanyWorkspace && !isConciergeTaskFlow} | ||
| onBackButtonPress={() => Navigation.goBack(ROUTES.ONBOARDING_PURPOSE.getRoute())} | ||
| onBackButtonPress={() => Navigation.goBack()} |
There was a problem hiding this comment.
Preserve the intent-list fallback after a refresh
When a user selects “Join a workspace” and then refreshes on the work-email URL, deep-link reconstruction leaves only WORK_EMAIL in the onboarding stack. Calling bare goBack() therefore pops the entire onboarding modal instead of returning to the purpose screen, so the visible Back button can take an incomplete-onboarding user out of the flow. Keep ROUTES.ONBOARDING_PURPOSE as the fallback so Back replaces the current route when the purpose screen is no longer in the stack.
Useful? React with 👍 / 👎.
|
already reverted on main? |
|
Yes, I believe this was reverted, and we can close this PR out, right @carlosmiceli? |
|
Yup! |
Reverts #103532