Conversation
MOZGIII
force-pushed
the
flow-integration
branch
from
fc99a8c to
ae41329
Compare
dmitrylavrenov
approved these changes
Jun 29, 2021
Contributor
Author
|
It's still a wip, doesn't work yet (I think :D). |
MOZGIII
force-pushed
the
flow-integration
branch
from
45e6563 to
6efe28e
Compare
dmitrylavrenov
force-pushed
the
flow-integration
branch
from
e40ed64 to
64f3416
Compare
MOZGIII
force-pushed
the
flow-integration
branch
2 times, most recently
from
39d0d50 to
6ad77ec
Compare
MOZGIII
force-pushed
the
flow-integration
branch
4 times, most recently
from
86bc112 to
87fc662
Compare
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
2 participants
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.
This PR adds the basic integration of the bioauth flow, together with the QR Code printing.
We've originally worked on adding tx submission in this same PR, but it turned out to be a rather challenging thing to tackle, so we've split out that part into a separate PR #38.
To do:
fix the issues with facetec api clientto be addressed in a separate PR