Skip to content
This repository has been archived by the owner on Feb 18, 2020. It is now read-only.

Feature/upgrade to web3 1.0 websockets #311

Open
wants to merge 27 commits into
base: develop
Choose a base branch
from

Conversation

W3stside
Copy link
Contributor

@W3stside W3stside commented Jul 26, 2018

Upgrading to Web3 1.0 BETA

What a pain in the ass...

WARNING: HIGHLY EXPERIMENTAL AND NOT STABLE

Changes:
  1. Upgrade Web3 0.20.2 > 1.0.0beta.xx
  2. Websocket provider
  3. Event listeners changed to new API spec
  4. checking for Events and saving TX's in state

Works like 50% of the time... everytime

Checklist:

  • - Do something if Websocket connection fails
  • - Write proper subscriptions and use better
  • - Fix saving TXs to state and the TransactionPanel
  • - Fix watcher function to only check for provider updates - remove updateMainAppState as used in middleware on new block detection
  • - ???

W3stside added 21 commits July 23, 2018 14:07
1. catch errors in async logic
    a. added try/catch in api inits
2. call fireListeners as non async
1. watcher function now in own module
2. shallow different in helpers
3. initialize no longer used
1. save txs, logs, events to state - reducer and actions in 1 file
2. create middleware to catch block updates and updateState
3. create TransactionPanel component to show tx's pending
4. add into router above Header for now
5. add middlewares to store, index files etc
1. refreshes when fail on load and wallet is unlocked
2. tokenList now checks auctions and is passed network
1. tx saving actions save current waiting txs to state
2. getTOkenList checks new tokens and dispatches avail auctions
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant