Closed oliver-day closed 1 year ago
web3Provider.listAccounts
check to see if the user already exists in the database, if they do, we can get their email address from their existing account. If they don't, the user hasn't created an account yet and we can collect their email address now.Rule of thumb: Try to limit work in a PR to about 1 day's work. Aim for 1-3 days from commit to main branch merge. See DORA Metrics.
When PRs get big like this, and merging won't break things, we have 2 options: break the PR into several smaller PRs and merge a little at a time, or open tickets for changes and go ahead and merge as-is.
Rule of thumb: Try to limit work in a PR to about 1 day's work. Aim for 1-3 days from commit to main branch merge. See DORA Metrics.
When PRs get big like this, and merging won't break things, we have 2 options: break the PR into several smaller PRs and merge a little at a time, or open tickets for changes and go ahead and merge as-is.
Are you ok merging this as is? Both the Magic Auth and connect sign up and sign in flows work currently.
I am planning on working on the adding the correct error handling next.
After that I will then work on the changes for the Magic Connect flows that we discussed.
Each issue will be it's own PR moving forward.
Are you ok merging this as is? Both the Magic Auth and connect sign up and sign in flows work currently.
Yep! Make sure all the conversations have resolutions or new issues, then click "resolve conversation" on each, and then merge. 🎉
Description
Changes address issues: #30 , #40
Current progress: demo
error-cause
package for handling errors from Magic