-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Conversation
Would prefer https://github.com/ethcore/parity/pull/3988 in first for the creation part since it reworks everything into a store. (Need to get through 1.5 release first before final checks on that one) |
The branches are not a clean merge at all, it has been completely re-done. (I18n, imports, formatting, store) Alternatively don't touch createAccount here and just do change as step 1. |
}; | ||
|
||
export default class PasswordStrength extends Component { | ||
|
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.
Extra unneeded line.
<div className={ styles.strength }> | ||
<label className={ styles.label }> | ||
<FormattedMessage | ||
id='passwordStrength.label' |
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.
prefer ui.passwordStrength.label
(top-level names reserved for views/modals, there is a lot of overlap with component-names)
} | ||
|
||
// Note that the suggestions are in english, thus it wouldn't | ||
// make sense to add translations to surrounding words |
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.
We cannot be 99.9% and once in we shouldn't need to come back. What are the alternatives?
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 clarify the above - at the very least all our text should be i18n. (3rd party could be non - for now). So the below should either just display the library hint or split it such that our part is translatable and their part a variable input.
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 has been taken care of)
return 'orange'; | ||
|
||
default: | ||
case 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.
case 0:
default:
(Or remove 0)
describe('rendering', () => { | ||
it('renders', () => { | ||
expect(render({ input: INPUT_A })).to.be.ok; | ||
expect(render({ input: INPUT_A }).find('LinearProgress')).to.be.ok; |
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.
Prefer seperate it blocks, otherwise you need to go by line to find the failure - one tests the component, the second parts of the component.
import React, { Component, PropTypes } from 'react'; | ||
import { debounce } from 'lodash'; | ||
import { LinearProgress } from 'material-ui'; | ||
import { FormattedMessage } from 'react-intl'; |
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.
While we are in this file and it is new, alphabetical order.
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.
Well it is, except for React which is the main dependency of this module, I don't think it's necessarily bad to have it on top.
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.
Would have expected at least the react-releated stuff to follow react, hence making exceptions jumbles it up and seems random. i.e. we typically do (not the case here)
import React from 'react';
import { FormattedMessage } from 'react-intl';
(grouped above, easy to see relations)
Here React is the exception, the rest sorted so it is a mix-match. Small thing (and driving me crazy), but like with everything, allows us to not have to think "in this case we do it differently".
Not a crisis, still worth being consistent about.
Okay, fixed grumbles and removed the |
Changes Unknown when pulling 74dc32d on ng-password-strengh into ** on master**. |
@gavofyork on your B0 -
|
* Added new PasswordStrength Component * Added tests * PR Grumbles
* verification: check if server is running (#4140) * verification: check if server is running See also ethcore/email-verification#67c6466 and ethcore/sms-verification#a585e42. * verification: show in the UI if server is running * verification: code style ✨, more i18n * fix i18n key * Optimized hash lookups (#4144) * Optimize hash comparison * Use libc * Ropsten fork detection (#4163) * Stop flickering + added loader in AddressSelector (#4149) * Stop UI flickering + added loader to AddressSelector #4103 * PR Grumbles * Add a password strength component (#4153) * Added new PasswordStrength Component * Added tests * PR Grumbles * icarus -> update, increase web timeout. (#4165) * icarus -> update, increase web timeout. * Fix estimate gas * Fix token images // Error in Contract Queries (#4169) * Fix dapps not loading (#4170) * Add secure to dappsreg * Remove trailing slash // fix dapps
Closes #4130
Add it to the account creation modals, and to the change password modal