-
Notifications
You must be signed in to change notification settings - Fork 9
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
Onboarding #56
Onboarding #56
Conversation
|
Did not think of how to "upgrade" an existing wallet, this is something we have to be careful with in the future (once the implementation stabilizes it won't be much of a problem). Fixed some of the apparently broken things with the PR, left a few things as is so it does not grow even more:
|
We can also make separated issues for that and just merge it. I take a look into the code then. |
@@ -77,3 +70,31 @@ unlocking-wallet = Unlocks.. | |||
adding-account = Adds new account.. | |||
loading-refresh = Loads transactions.. | |||
sending-funds = Sending funds.. | |||
|
|||
# Onboard | |||
onboard-button-back = Back |
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.
Do we want to use a prefix for everything? Like onboard__ and create__ or something similar?
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 it can be smart so that we know the context of the text. However, when we finish with most of the text it's probably easier to see what are the common things, and what we might need context for (if any).
@@ -22,18 +26,20 @@ const elementSelector = (selectedElement) => { | |||
let navigation = new Navigation([], elementSelector); | |||
|
|||
loadedComponentStore.subscribe((value) => { | |||
if (value.elements.length > 0) { |
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.
Why did you remove it? If the elements are empty, it shouldn't create a navigation and attach keydown listener to it.
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.
Because we need to initialize this to set/unset selection and navigation on view change. So even though elements are an empty array, we need to know that in order to do right thing in for instance "Enter" case.
}; | ||
export function generateWallet(): Promise<WalletResult> { | ||
return new Promise((resolve) => { | ||
setTimeout(() => { |
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.
What is this setTimeout for?
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.
To be able to delay the function, so that we can show the loading screen. There might be a more ideomatic way to do this though..
Fixed the inconsistencies, and added a few of the unknown issues as new issues. Thanks for testing! |
Added a proper flow for onboarding. Placeholder texts and values so far! Let me know what you think.