You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+11-10Lines changed: 11 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
# CHANGELOG
2
2
3
-
## 1.32.0-beta.x
3
+
## 1.32.1 Sep 7, 2020
4
4
5
-
Upgrade priority: Low. However with the changes to connect/disconnect behavior, if using this to tracks state mnually inside your application an upgrade is recommended.
5
+
Upgrade priority: Low. Recommended when manually using provider connect/disconnect or using multiple instances in a single process.
6
6
7
-
-**Breaking change** Previously `isReady` could throw and error, now it will always succeed on connection. For trapping errors, use the `.isReadyOrError` variant on the API
8
-
-**Breaking change** The `isConnected` provider interface is now a getter, previous calls to `provider.isConnected()` should now be done via `provider.isConnected`. Likewise the `provider.disconnect()` is now async returning a Promises to complete alignment of intent.
7
+
-**Breaking change** Previously `.isReady` could throw an error, now it will always succeed on connection. For trapping errors, use the `.isReadyOrError` variant on the API
8
+
-**Breaking change** The `isConnected` provider interface is now a getter, replacing previous calls to `provider.isConnected()`. Additionally the `provider.disconnect()` is now async, aligning with `.connect()`.
9
9
10
10
Contributed:
11
11
@@ -14,18 +14,19 @@ Contributed:
14
14
15
15
Changes:
16
16
17
-
- Adjust memoization to work on a per-instance basis, instance shared between API and Provider instances
17
+
- Adjust memoization to work on a per-instance basis, with no contamination between multiple api/provider instances
18
18
- Added `derive.chain.getBlock(hash)` to retrieve a `SignedBlock` extended with an `.author` (same as `derive.chain.getHeader(...)`)
19
-
- Added `api.{connect, disconnect}()` as well as `isConnected` interfaces. The first functions returning `Promise<void>`
20
-
- Error on provider connections will now emit and error (as expected) via the event emitter
21
-
-Add `api.derive.accounts.accountId` to perform AccountId lookups (from indices or actual AccountId)
19
+
- Added `api.{connect, disconnect}()` as well as `isConnected` interfaces. The first functions async returning `Promise<void>`
20
+
- Error on provider connections will now emit all (as expected) via the event emitter
21
+
-Ensure that initial connection failures always retry (when using auto-connection management)
22
22
- The `api.derive.staking.query/queryMulti` no longer retrieves session keys (can be done via `.keys/keysMulti`)
23
+
- Add `api.derive.accounts.accountId` to perform AccountId lookups (from indices or actual AccountId)
23
24
- Lessen load of `paymentInfo` queries to only use accounId mappings as available
24
25
- Adjust staking derives to cater for early Substrate 2.0 chains (optional/non-optional EraIndexes)
25
26
- Cater for the handling of nested aliased types, e.g. wrapped inside Vec or Tuple
26
27
- Add the support for the `grandpa_subscribeJustifications` RPC
27
-
- Adjust `Call.toHuman()` to remove more technical internal details
28
-
-static metadata & tests updated for the latest substrate master
28
+
- Adjust `Call.toHuman()` to remove decoding-related technical internal details
29
+
-Static metadata & tests updated for the latest substrate master
29
30
-`toHuman()` & `.toBigInt()` has been explicitly added to the API documentation
30
31
- Adjust known types for latest Kusama network state
0 commit comments