embark/packages/embarkjs
Pascal Precht 2ae46640e9 feat(@embarkjs/ens): Introduce `dappConnection` configuration for namesystem
This commit removes the need for `EmbarkJS.onReady()` and `EmbarkJS.Blockchain.blockchainConnector` APIs
in the ENS provider implementation and instead relies purely on vanilla `Web3`. This comes
with the effect that `EmbarkJS.Names` needs to figure out itself what to connect
to, as well as when a connection has been established.

To make that possible, `EmbarkJS.Names` now implements a similar algorithm to
`EmbarkJS.Blockchain` that tries to connect different endpoint, given a `dappConnection`
configuration.

If no `dappConnection` configuration is given via `namesystem.json`, Embark will fallback
to the same connection list that's provided in `contracts.js|json`.

wip
2019-12-09 12:07:03 +01:00
..
embarkjs chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00
ens feat(@embarkjs/ens): Introduce `dappConnection` configuration for namesystem 2019-12-09 12:07:03 +01:00
ipfs chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00
swarm chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00
web3 chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00
whisper chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00