v1.32.1
Upgrade priority: Low. Recommended when manually using provider connect/disconnect or using multiple instances in a single process.
- Breaking change Previously
.isReadycould throw an error, now it will always succeed on connection. For trapping errors, use the.isReadyOrErrorvariant on the API - Breaking change The
isConnectedprovider interface is now a getter, replacing previous calls toprovider.isConnected(). Additionally theprovider.disconnect()is now async, aligning with.connect().
Contributed:
- Expand vesting information via derive balances (Thanks to https://github.com/niklabh)
- Add
isReadyOrErrorto API,isReadyalways succeeds (Thanks to https://github.com/shawntabrizi)
Changes:
- Adjust memoization to work on a per-instance basis, with no contamination between multiple api/provider instances
- Added
derive.chain.getBlock(hash)to retrieve aSignedBlockextended with an.author(same asderive.chain.getHeader(...)) - Added
api.{connect, disconnect}()as well asisConnectedinterfaces. The first functions async returningPromise<void> - Error on provider connections will now emit all (as expected) via the event emitter
- Ensure that initial connection failures always retry (when using auto-connection management)
- The
api.derive.staking.query/queryMultino longer retrieves session keys (can be done via.keys/keysMulti) - Add
api.derive.accounts.accountIdto perform AccountId lookups (from indices or actual AccountId) - Lessen load of
paymentInfoqueries to only use accounId mappings as available - Adjust staking derives to cater for early Substrate 2.0 chains (optional/non-optional EraIndexes)
- Cater for the handling of nested aliased types, e.g. wrapped inside Vec or Tuple
- Add the support for the
grandpa_subscribeJustificationsRPC - Adjust
Call.toHuman()to remove decoding-related technical internal details - Static metadata & tests updated for the latest substrate master
toHuman()&.toBigInt()has been explicitly added to the API documentation- Adjust known types for latest Kusama network state