-
Notifications
You must be signed in to change notification settings - Fork 33
Conversation
todo: * add option to export json keyfile to backup * clean up duplicated code in store
uses react-dropzone
…into yj-json-keyfile
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.
cool :)
I tried exporting to json an existing account in Fether and importing it again and it gave me an account with a different address than that in the json file, not sure why that is
packages/fether-react/src/Accounts/CreateAccount/AccountRewritePhrase/AccountRewritePhrase.js
Outdated
Show resolved
Hide resolved
packages/fether-react/src/Accounts/CreateAccount/AccountRewritePhrase/AccountRewritePhrase.js
Outdated
Show resolved
Hide resolved
packages/fether-react/src/Accounts/CreateAccount/AccountRewritePhrase/AccountRewritePhrase.js
Outdated
Show resolved
Hide resolved
move jsonbackup to its own component/route lint lint
Also take a look at my proposals to add more menu items at #264 |
no drop, only browse for file lint
This is looking really good! I have a similar problem as the one mentioned by Axel. Importing an account that I have gives me a different one at the import. I noticed that the account doesn't have We should be extra careful I think and ask for a password confirmation. This doesn't make the UX so much worse, and we better make sure the user did not mistype his password. Also this makes the password screen quite large, I'd rather have a different screen rather than a dropped view, and we can add a little explanation to guide users. Something like: "Choose a password to encrypt Json keystore file". |
Cool, all my previous comments are solved. Nit: It'd be nice to accept any sort of file, Parity produces keystore file names without I had one weird behavior, when importing an account:
edit: just realized this is everywhere.. so we might address this in another PR. |
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.
Some nits:
- the
next
button should be in the recovery phrase card and centered (see inline comment) - focus the "password" field at import and export
- map the
enter
key to the "confirm account import" and "backup account" buttons (now on the back)
Otherwise looks great :)
<br /> | ||
<Card> {phraseCard} </Card> | ||
<br /> | ||
{this.renderButton()} |
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.
Can we put the next button in the "phrase card" as it's only relevant to this one, I believe it should be centred as well as are buttons usually.
Not sure you expected a review on this yet (simply change the label to "please review" when you think we should have a look)
|
@Tbaut, I think it'd be best to make the "focus on password field" a separate PR as it'd involve refactoring the Form Fields as stateful components so we can use React refs etc. That PR would also fix the current behavior where pressing Enter maps to the Back button in a much simpler way than the past couple commits which detects the keyPress events and keyCodes per form, blabla... but doesn't relate to json import particularly. I will raise this as a separate issue and PR. |
56ff553
to
9aa209d
Compare
[clabot:check] |
It looks like @yjkimjunior hasn't signed our Contributor License Agreement, yet.
You can read and sign our full Contributor License Agreement at the following URL: https://cla.parity.io Once you've signed, please reply to this thread with Many thanks, Parity Technologies CLA Bot |
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.
My local branch was running crazy, I did a complete test:
- recovery from phrase
- export from account
- import account (previously exported)
all works well, thank you so much :)
@yjkimjunior Can you rebase/merge lastest master? |
[clabot:check] |
It looks like @yjkimjunior signed our Contributor License Agreement. 👍 Many thanks, Parity Technologies CLA Bot |
#101
…
todo:
add option to export json keyfile to backup from Accountjson encoding checkclean up duplicated code in storeadd import options screen