Fixe web3.eth.accounts encrypt/decrypt lib #1237
Closed
This pull request is big! We’re only showing the most recent 250 commits.
Commits on Mar 7, 2017
Commits on Mar 10, 2017
Commits on Mar 14, 2017
Commits on Mar 16, 2017
Commits on Mar 20, 2017
Commits on Mar 22, 2017
Commits on Mar 28, 2017
Commits on Mar 29, 2017
Commits on Mar 30, 2017
Commits on Jun 28, 2017
-
* improve auto detection of providers * added detection provider tests * add more tests and changed docs
Commits on Jun 29, 2017
-
* added whisper api * added whisper tests * added ipc provider docs * working on docs * added whisper docs * small test change
Commits on Jun 30, 2017
Commits on Jul 5, 2017
-
* added swarm-js * modified docs * added swarm provider * added swarm docs, tests missing
Commits on Jul 13, 2017
-
* Initial implementation of web3.eth.accounts * Use EthFP internally * Getting accounts closer to the desired api * Style changes * Partially implement web3.eth.accounts.wallet as specified * moved accounts to its own package * docs changes * Change gasLimit to gas * changed Accounts to class * added wallet access to sendTransaction * changing docs, in progress * improved docs and changed accounts package * fixed tests * fixed jshints * added wallet tests * added signTransaction tests for async signing * added signTransaction tests with iban addresses * changed EthFP -> EthLib * added account decrypt function * added wallet decrypt and encryption function * added decrypt and encryption tests * added account generation tests * made load save wallet work * added more static tests * added eth_sign tests * fixed lint errors * fixed travis
-
-
Commits on Jul 17, 2017
Commits on Jul 18, 2017
Commits on Jul 19, 2017
Commits on Jul 20, 2017
Commits on Jul 21, 2017
Commits on Jul 24, 2017
Commits on Jul 26, 2017
-
-
-
-
-
-
-
-
Do not import node libs on browser. Fixes #923
I'm assuming the problem happened when web3 was imported with require, and then webpack was used on it. If so, this was probably caused because I was incorrectly importing Node.js related libs on the browser release. This fixes it by correctly using the browser field on package.json.
Commits on Jul 27, 2017
-
Increment Swarm version. Fixes #923
Includes the swapping of the mimetypes library on swarm-js, which fixes another issue with webpack.
-
-
-
-
-
fix TransactionConfirmation for InstantSeal (#936)
* fix TransactionConfirmation for InstantSeal since parity --chain dev is using its InstantSealEngine and creating Block as soon as a new Transaction is send, the subscribed event for the new BlockHeader will come too late. This results in a waiting forever for a new Block, which never comes. So we should first check whether the transaction has already been mined before subscribing for new Blocks. * fixed format and added bind * keep on listing only if listeners are registered * fixed tests * added test for instantSeal * cleanup
-
-
-
-
-
Commits on Aug 8, 2017
Commits on Aug 16, 2017
-
web3.personal => web3.eth.personal.
Commits on Sep 11, 2017
Commits on Sep 15, 2017
-
Typo on the method name
-
-
`soliditySah3` -> `soliditySha3`
-
-
-
Fix external links in the docs (#999)
* fix missing ">" fix missing ">" in the external link syntax in the docs * fix one more link in the docs * update ABI external link in the docs
-
-
-
-
Sanitize
tx.tofor invalid address (#982)As `testrpc` or other sources send `0x0` instead of `null` in transaction object when contract is created.
-
-
-
Fix unreliable array test in Contract package (#1013)
Using node.js 6.11.2 I get the following error when trying to instantiate contracts: > jsonInterface instanceof Array true > new web3.eth.Contract(jsonInterface) Error: You must provide the json interface of the contract when instatiating a contract object. Although jsonInterface instanceof Array evaluates to true, the exact same test condition evaluates to false within the Contract constructor with the passed down json interface. Using either "Array.isArray(jsonInterface)" or "toString.call(jsonInterface) === '[object Array]'" as a test condition instead fixes the issue. Also the typo in the error message got corrected.
-
fix asynchronous send request method backend bug. fixes #1014 (#1018)
resolve asynchronous send request method error by using sendAsync function when running on the backend (Node.js)
-
Support for https and wss providers (#1031)
* Support for https and wss providers Fixes a "Can't autodetect provider for " error that's returned currently with Infura nodes. * Update index.js
-
Various grammar changes for web3-eth-contract.rst (#1024)
Fixed various small grammar issues in documentation
-
Commits on Sep 18, 2017
-
Make web3 as package in lerna packages (#1045)
* make web3 as main package in lerna * modify web3 require path for testcases * change build process for web3 * change build process for web3 package
-
Commits on Sep 19, 2017
-
-
allow empty address arguments when encoding abi params (#1047)
* allow empty address arguments * add test for address encoding
-
-
-
-
-
Commits on Sep 20, 2017
-
added typedefintions for web3 (#897)
* added typedefintions * more sha3-args * merged web3 * fixed account
-
-
-
Commits on Sep 25, 2017
Commits on Sep 26, 2017
Commits on Oct 4, 2017
-
if multiple events, return array (#1048)
* return array of events if multiple This fixes a bug where if a transaction emitted multiple of the same events, the transactionReceipt only returned 1 of them. We now return an object for the event if there is only 1. If there are multple of the same events, then we return an array of event objects * update docs and create new test * remove spacing changes
-
Decouple wallet.length from other wallet functions (add, encrypt, cle…
…ar) (#1079) * Added wallet._findSafeIndex to prevent wallet.create overwrites. * Added tests for wallet overwrite patch. Updated Chai to 4.0. All tests pass with new test and new Chai. * Strengthened test with inequility check. Changed naming for readability. * Fixed similar issue with wallet.clear and wallet.encrypt. The coupling of wallet.length to other wallet functions causes issues when accounts have been previously removed. * Added test for wallet encrypt/decrypt. Fixed wallet.encrypt
Commits on Oct 10, 2017
-
Ensure websocket connection is open before sending (#1078)
* Ensure websocket connection is open before sending to prevent unhandled error. * [console] remove trace on ws error * Trigger tests rebuild * [formatting] add semicolons;
-
-
Commits on Oct 17, 2017
Commits on Oct 18, 2017
Commits on Oct 19, 2017
-
-
* prepare release * update eth-lib and added api changes * updated dist/web3.min.js * updated eth-lib to 0.2.5 * add warning to the accounts docs
-
-
-
Commits on Oct 20, 2017
Commits on Oct 23, 2017
Commits on Oct 24, 2017
-
Fixes to TypeScript definitions (#1131)
* removed privateKey from web3.eth.signTransaction and web3.eth.accounts.signTransaction documentation * removed privateKey from web3.eth.signTransaction and web3.eth.accounts.signTransaction documentation * added vscode to gitignore and minor doco change * Added test to show privateKey can not be passed to accounts.signTransaction * removed passing of private key * Added Eth.signTransaction function renamed accounts.privateToAccount to accounts.privateKeyToAccount Added missing Contract.options Added status to TransactionReceipt * reversing changes so my forked 1.0 branch is in sync with the upstream 1.0 branch
-
* Fix for Bug #1123 * Trigger travis * Removed a bogus test for `bytes64`
-
-
Commits on Nov 13, 2017
-
-
correct personal.newAccount Promise resolve value (#1157)
Docs currently show boolean, but it is returning a string
-
-
-
-
Fixes in types definition (#1139)
* Fixes in types definition * Fix Provider type: implement 'empty' variables to the other providers interfaces to make a OR between them
-
Step 1 of moving to ES6 (#1149)
* First draft of babel+eslint+rollup * Moved to gulp 4, improved some logging output during builds. * Tweaks to the build process. * Fixing the versioning task. * Created separate copies of the .eslintrc files, one for each package.
-
Commits on Nov 14, 2017
Commits on Nov 27, 2017
-
Feature/es6 first tests (#1152)
* First draft of babel+eslint+rollup * Moved to gulp 4, improved some logging output during builds. * Tweaks to the build process. * Fixing the versioning task. * Created separate copies of the .eslintrc files, one for each package. * Started converting the first of the tests to es6. Started by converting HttpProvider to es6, which led to the conversion of contract.js, eth.sendTransaction.js, and setProvider.js Enabling ES6 support in Mocha led to fixes in method.buildCall.js and utils.sha3.js Fixed the problems in test/eth.sendTransaction.js that were causing the error "Transaction was not mined within 50 blocks, please make sure your transaction was properly send. Be aware that it might still be mined!". There may be deeper issues with the tests in eth.sendTransaction.js, these will require some conversation with Fabian before moving forward. * Fixing coverage problems by upgrading to nyc (the new istanbul) * Fixed test failure on node 8
Commits on Dec 1, 2017
-
Converted the rest of the tests to es6 (#1203)
* Converted the rest of the tests to es6 * Switched back to "dot" reporter for mocha. Removed stray console.error line that should not have been committed. Removed dead/commented console.log lines elsewhere in the code.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.