- Jan 07, 2019
-
-
Axel Chalon authored
- Add option to import a Parity Signer account. It is then stored in local storage. - Send transactions with Parity Signer accounts - Refactor sendStore so that "token" (and chainId) is inside this.tx; avoids having to pass `token` around every function, and it makes sense to put it in the object since it is part of the tx info. - Add account type (either node or signer) to accountsInfo - Add account type to withAccount; output props are now `{account: {address, type}}` instead of `{accountAddress}`
-
- Jan 06, 2019
-
-
Luke Schoen authored
* Move toggle details buttons and associated methods and showDetails state into nav of TxForm component * Pass showDetails down as props to TxDetails * Remove previous attempt to display TxDetails like a popup above other fields (i.e. remove form-details-wrapper and -details-value styles)
-
- Jan 04, 2019
-
-
Luke Schoen authored
* Move "Details" / "Hide" buttons into the form-nav footer section * TxDetails now appears above the footer area above other input fields without causing the screen height to increase * Background of the TxDetails darkened so it stands out from surroudings * Change "Details" arrow to point upwards since TxDetails now shown above * Change "Hide" arrow to point downward since TxDetails now shown above * Rename classnames to `_` or `-` more consistently * Note: To quickly display the 'Details' button so you can click it change TxForm.js as follows: ``` {/* {valid && this.estimatedTxFee(values) ? ( */} <TxDetails // estimatedTxFee={this.estimatedTxFee(values)} estimatedTxFee={new BigNumber('8100000')} token={token} // values={values} values={ { amount: new BigNumber('0.1'), gasPrice: new BigNumber('21000') } } /> {/* ) : null} */}
-
Luke Schoen authored
-
Luke Schoen authored
review-fix: Hide vertical overflow on body element so scrollbar not flicker on/off when TxDetails toggled
-
Luke Schoen authored
-
Luke Schoen authored
-
Luke Schoen authored
-
Luke Schoen authored
-
Luke Schoen authored
-
Luke Schoen authored
-
Luke Schoen authored
-
Luke Schoen authored
-
- Jan 03, 2019
-
-
YJ authored
-
Luke Schoen authored
Note: It is necessary to have no indentation otherwise spaces are interpreted. See discussion of options: https://github.com/paritytech/fether/pull/307#discussion_r244695598
-
Luke Schoen authored
-
- Jan 02, 2019
-
-
Luke Schoen authored
-
Luke Schoen authored
* Remove `isEstimatedTxFee` since can just use `estimatedTxFee` to achieve same functionality * Rename `newEstimatedTxFee` to `newGasEstimate` since it returns a value that's used for the `values.gas` prop * Update `estimatedTxFee` to return `null` if the amount, gas, gasPrice values provided aren't valid, instead of returning the calculated estimated tx fee * Wrap call to `estimateGas` in a try/catch block that throws error "Unable to estimate gas" when error thrown when calling `estimateGas` in TxForm.js * Move check `if (!ethBalance) {` earlier in function
-
YJ authored
-
YJ authored
-
YJ authored
-
Amaury Martiny authored
-
Amaury Martiny authored
-
YJ authored
-
Luke Schoen authored
-
Luke Schoen authored
-
Luke Schoen authored
-
Luke Schoen authored
-
- Jan 01, 2019
-
-
Luke Schoen authored
-
Luke Schoen authored
* Create TxDetails component and move relevant instance methods from TxForm into TxDetails * Fix linting warning `Using target="_blank" without rel="noopener noreferrer" is a security risk: see https://mathiasbynens.github.io/rel-noopener`
-
Luke Schoen authored
* Remove isCancelled * Remove estimatedTxFee from state * Sort instance methods into alphabetical order * Refactor by adding isEstimatedTxFee to check gas properties defined on form values * Add instance method estimatedTxFee to return calculation based on gas values * Move functions out of render function and change them into instance methods * Remove duplicate check for whether values.gas existed
-
Luke Schoen authored
-
- Dec 31, 2018
-
-
Luke Schoen authored
-
Luke Schoen authored
-
Luke Schoen authored
-
- Dec 27, 2018
-
-
Luke Schoen authored
* Fixes error `Uncaught TypeError: Cannot read property 'resolve' of null at flush` that is generated after both valid amount and recipient values are entered
-
Luke Schoen authored
-
Luke Schoen authored
-
- Dec 26, 2018
-
-
YJ authored
-
- Dec 25, 2018
-
-
YJ authored
-