Repository navigation
Conversation
…t one The funnel counts a path as completed when it ends on a last screen. A screen whose only buttons take the user back to a screen they had to pass (a custom Back, Start over) is a last screen, and a screen that leads on to any other screen, also one higher in the screen list, is not. Say so instead of "no navigation to another screen". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Author
|
Closing: #822 rewrote this section on main, and its wording ("a screen with nowhere further to go", the same as in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
One sentence on the Flow funnel page, in the "Completed" rules: what a last screen is.
Before: "A last screen is a screen with no navigation to another screen."
After: "A last screen is a screen with no navigation onward. A button that only takes the user back to a screen they had to pass to get there, such as a custom Back or Start over button, doesn't count as navigation onward."
Why
The flow transformer marks a screen as the last one by this rule now (released today). Before, a screen that moved to a screen higher in the builder's screen list could be marked last by mistake, so users who left a branching flow in the middle counted as completed. A final screen with a hand-made Back or Start over button stays the last one, so the old sentence ("no navigation to another screen") no longer matches.
The flag is set when a flow version is published, so versions published before the release keep the old flags until they are published again.
Only the English source is changed; the locale files are translated by the workflow on merge.
🤖 Generated with Claude Code