-
Notifications
You must be signed in to change notification settings - Fork 82
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
feat(Onboarding): Create Profile & Login flows #16722
Conversation
Jenkins BuildsClick to see older builds (590)
|
fe0f177
to
315bbc0
Compare
ad67a76
to
35e9ad5
Compare
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.
Huge work!
Nothing major found.
ui/StatusQ/src/StatusQ/Controls/StatusPasswordStrengthIndicator.qml
Outdated
Show resolved
Hide resolved
ui/StatusQ/src/StatusQ/Controls/StatusPasswordStrengthIndicator.qml
Outdated
Show resolved
Hide resolved
@@ -75,6 +74,11 @@ Item { | |||
input text. | |||
*/ | |||
property ListModel filteredList: ListModel { } | |||
|
|||
property bool isError |
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.
Should this be hasErrror
instead?
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.
Yeah maybe, just followed what we have elsewhere 🤷
} | ||
StatusBaseText { | ||
Layout.fillWidth: true | ||
text: qsTr("You will require your Keycard to log in to Status and sign transactions") |
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 sentence sounds a bit weird. I'm not sure what we're trying to tell the user
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.
Not sure either, pre-existing code 🤷
ListItemButton { | ||
objectName: "btnBySyncing" | ||
Layout.fillWidth: true | ||
text: qsTr("Log in by syncing") // FIXME wording, "Log in by pairing"? |
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.
Did we confirm if we want Pairing instead? cc @benjthayer
I personally like it better
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.
Yeah, not sure now; I added a FIXME there, this needs a systemic approach
@@ -187,7 +187,7 @@ SettingsContentBase { | |||
anchors.left: parent.right | |||
anchors.leftMargin: 8 | |||
anchors.verticalCenter: parent.verticalCenter | |||
tooltipText: qsTr("Connection problems can happen.<br>If they do, please use the Enter a Seed Phrase feature instead.") | |||
tooltipText: qsTr("Connection problems can happen.<br>If they do, please use the Enter a Recovery Phrase feature instead.") |
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.
Everywhere else, we don,t capitalize. I assume the old copy was just a mistake
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.
Maybe... existing code 🤷
e505b50
to
adb3474
Compare
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.
LGTM, assuming we create a backlog for further improvements and fixes
45b7c0c
to
5a6613a
Compare
- implement the basic Onboarding UI skeleton and the Create Profile flows - adjust the PasswordView and EnterSeedPhrase views to the latest design - add the main OnboardingLayout and StatusPinInput pages to Storybook - change terminology app-wide: "Seed phrase" -> "Recovery phrase" - implement the Login flows (seed, sync, keycard) - amend the keycard flow sequences with separate (non) empty page Fixes #16719 Fixes #16742 Fixes #16743
- extend the tests to verify whether we collected the correct data - restore the "pointing hand" cursor on clickable elements - some minor improvements
- instead of the factory reset when the keycard is locked
- they are not very useful (and were outdated anyway)
5a6613a
to
80f4bca
Compare
a6d3044
to
d5524fd
Compare
d5524fd
to
35b8620
Compare
i will check what is happening with tests |
okay i can reproduce the problem. There is a performance degradation it seems) - clicking |
@caybro i fixed the tests in PR to let them pass, however lets wait to merge this PR , i am running all tests i have to catch any other changes in another tests that are not running in PRs |
29ce4b0
to
43a5b68
Compare
i fixed everything i wanted @caybro |
What does the PR do
Create profile UI flows:
Fixes #16719
Fixes #16742
Fixes #16743
Login UI flows:
Fixes #16798
Fixes #16799
Fixes #16800
Fixes #16977
Affected areas
Onboarding
Architecture compliance
My PR is consistent with this document: Status Desktop Architecture Guide
Screenshot of functionality (including design for comparison)