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.
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
EP-2518 Remove ConfirmationStep #1119
base: EP-2517-branded-checkout-improvements
Are you sure you want to change the base?
EP-2518 Remove ConfirmationStep #1119
Changes from 19 commits
9f2ceef
7125463
170dcf3
2d059f4
9d95c84
aa1ced2
af56314
43e9cac
3a7a60a
64b70dc
446bfbb
8e101e9
374cce9
fb042a2
af339ac
05028d2
41214a1
b629164
d71a122
b756b17
dc73810
fc2fe5d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I'm going to dig deeper, but I'm hoping I can find a way to not have to recreate this logic here by including step-3 on this step-1 page.
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.
I'm sure it's possible, but there will be more branching in
step-3
. The tricky part will be changingstep-3
to accept a new prop that lets us save the 3 forms and wait for them to finish saving before doing the submission.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.
Or we could possibly do the handling of the 3 forms in an intermediary, invisible-to-the-user step?
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.
I guess, step-3 itself has review data in the template, so we probably don't want to use it directly; however, it might make sense to refactor the common logic out to a service and use it in both places (step-3 and branded-step-1)
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.
This may not be needed when we move to enterprise. At this point I've removed it, but may need to do something with it after QA.
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.
I think we were going to put these error messages in a separate component.