Skip to content

backport(510) next does not work as expected in ComponentFlow #513

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

Jump to bottom
Closed
jvalkeal opened this issue Aug 22, 2022 · 0 comments
Closed

backport(510) next does not work as expected in ComponentFlow #513

jvalkeal opened this issue Aug 22, 2022 · 0 comments
Labels
type/backport Is a issue to track backport, use with branch/xxx
Milestone
2.1.2

Comments

@jvalkeal
Copy link
Contributor

Backport #510
@jvalkeal jvalkeal added the type/backport Is a issue to track backport, use with branch/xxx label Aug 22, 2022
@jvalkeal jvalkeal added this to the 2.1.2 milestone Aug 22, 2022
jvalkeal added a commit that referenced this issue Aug 22, 2022
@jvalkeal
Fix next handling in ComponentFlow
2cf7123 
- This fixes a bug where returning null from a next()
  didn't stop a flow.
- Backport #510
- Fixes #513

(cherry picked from commit 7c4700b)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/backport Is a issue to track backport, use with branch/xxx
Projects
None yet
Milestone
2.1.2
Development

No branches or pull requests
1 participant
@jvalkeal