This repository has been archived by the owner on Sep 27, 2019. It is now read-only.
Releases: trufflesuite/drizzle-legacy
Releases · trufflesuite/drizzle-legacy
v1.1.4
Updates:
- Added sensible default options. See the
src/defaultOptions.js
file. - Replaced block polling via
setInterval
witheth-block-tracker-es5
for more reliable block data when websockets are unavailable.
v1.1.3
Fixes:
- No longer have to include an
events
key in the options object.
v1.1.2
v1.1.1
v1.1.0 - Real World Readiness
As the name implies, this release contains features that allow Drizzle to function in more real-world scenarios including MetaMask support and using your existing redux store! 🌎🌍🌏
New Features
- BYOS (Bring Your Own [redux] Store)
- Can accommodate mono-store and multi-store setups in addition to a Drizzle-created store. See the documentation for implementation details.
- Tracks account balances.
- Account, account balance and block polling.
- Drizzle will now use block polling as a fallback for providers that don't support subscriptions.
- Custom intervals (see options below).
- New options
- polls (object): Contains key/value pairs denoting what is being polled and the interval (in ms). Possible polls are accounts and blocks. Accounts will poll for addresses and balances, blocks for new blocks. Blocks default to 3000. For example:
polls: { accounts: 1500 }
.
- polls (object): Contains key/value pairs denoting what is being polled and the interval (in ms). Possible polls are accounts and blocks. Accounts will poll for addresses and balances, blocks for new blocks. Blocks default to 3000. For example:
- Distribution minified.
Drizzle v1.0.1 - Comet ☄️
You may have seen this repository whizzing by as you gazed at our GitHub. Well, it's finally ready for study! Introducing Drizzle: A collection of front-end libraries that make writing dapp front-ends easier and more predictable.
Why version 1.0.1? Because we want to keep the GitHub releases in sync with the NPM package versions.
What's inside? Glad you asked. Rather than repeat ourselves, check out the detailed readme or our documentation. For future releases, these notes will document fixes, additions, subtractions and changes.