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
Complete account linking in authflow #4159
Conversation
…ype of account linking
pkg/lib/authenticationflow/declarative/intent_check_conflict_and_create_identity.go
Outdated
Show resolved
Hide resolved
Ready for review, |
@@ -74,7 +74,7 @@ func (i *IntentSignupFlowStepIdentify) GetVerifiableClaims(_ context.Context, _ | |||
return nil, nil | |||
} | |||
|
|||
m, ok := authflow.FindMilestoneInCurrentFlow[MilestoneDoCreateIdentity](flows.Nearest) | |||
m, ok := authflow.FindFirstMilestone[MilestoneDoCreateIdentity](flows.Nearest) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems using milestone with nested steps could easily cause bugs, I am thinking about should we redefine milestone as "node / intent created by this intent". i.e. We always search in flows.Nearest only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. I think we need to review the existing usage of milestone, and classify each usage into different groups. If we only have a group ("node / intent created by this intent"), then we can change the behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created an issue https://linear.app/authgear/issue/DEV-1245/revise-usage-of-milestones-in-authflow for this
ref #4134 #4146
ref DEV-1223 DEV-1231