To avoid issues with installation it is necessary to install a compatible version of Yarn.
It was highlighted [here](https://github.com/polkadot-js/apps/pull/78) that Yarn 1.0 included workspaces, and we are successfully using Yarn 1.3.2 for Travis CI, so propose to request users to ensure they are using a version later than that to avoid and problems.
For instance, I was using Yarn 0.24.6 and it [wouldn't install the sub-package dependencies](https://github.com/polkadot-js/apps/pull/78) nor would it [run a necessary binary](https://github.com/polkadot-js/apps/issues/98), but after upgrading to Yarn 1.7.0 those issues were resolved.
* fix: Fixes#88 buttonbar style cornering on Accounts and Addresses pages
- Add right corners to Forget
- Add left corners to Reset
* refactor: Move overrides for buttonbar corner styles into shared resource
* fix: Add newline to end of file
* refactor: Refactor using PostCSS variables, nesting, and import
* refactor: Move variables into partials subfolder. Apply CSS when preceding sibling is spacer
* fix: Remove unnecessary comma to pass CI linting
* fix: Add initial divider with no padding to apply corners conditionally
There is no CSS selector combinator that allows conditional styling of an element conditional upon "subsequent" sibling elements existing. This is a work-around whereby a dummy divider with no padding is added to the start of the button group such that the custom corner overrides only apply to button groups that contain a 1st and 3rd element that are dividers. Only options for conditional styling dependent on "preceding" sibling elements currently exist that are compatible across browsers (i.e. 'Adjacent sibling combinator' by use of `+` and 'General sibling combinator' by use of `~`, see below reference for details).
Another alternative solution that was considered by not deemed generic enough was to conditionally apply the custom cornering only to button groups that are contained within a classname that contains the text "--Editor", on the assumption that the Forget, Reset, Save button group would only be used within a nesting containing such a wildcard value (as is currently the case)
```
div [class*="--Editor"] {
.ui--Button-Group {
.ui.buttons {
.button:nth-child(1) {
border-top-right-radius: $small-corner;
border-bottom-right-radius: $small-corner;
}
.ui.button.compact.mini.basic + .button:nth-child(3) {
border-top-left-radius: $small-corner;
border-bottom-left-radius: $small-corner;
}
}
}
}
```
Reference: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Selectors
* fix: Resolve linting CI errors
* fix: Add missing dependencies to package.json to pass CI
* refactor: Move widthless divider into base Group component
* refactor: Move button group custom cornering styles
* feat: Fixes#75. Add edit icon from semantic-ui to account name input field
Adding an edit icon that is embedded in the account name input field makes it more obvious to the user that the input field isn't read-only, and that there is a way to "click before doing" (i.e. editing the input field that is identified as being editable before the ability to save changes is granted). Some users may click the edit icon itself thinking it toggles the ability to edit the input field, whilst others may just recognise that the edit icon means the input field is editable. In either case just having the edit icon should suffice as being the initial "call to action" for a user wishing to edit the input field, and since the Reset and Save buttons illuminate when the account name is modified, they'll recognise that a further step is required to save their changes.
* resolve introduced ESLint and Flow errors
* fix: Move attributes up so they are in alphabetical order
* fix: Remove unnecessary classenames. Edit icon stays within input field
