Important Current versions of Polkadot/Substrate have dropped support for linked maps on storage entries. If you are using these queries to retrieve all entries, for instance staking.{nominators,validators}() and using an upgraded chain, you need to swap to retrieving entries via .entries() or .keys() for the keys.
Pull in support and types for latest Polkadot/Substrate
Add support for the new Substrate state_getKeysPaged RPC, including use in storage keys
Move derive.staking.controllers to derive.staking.stashes, reflecting actual content
Cater for adjusted storage (non-linked mapped) for derive.staking.stashes queries (with old-compat)
Expanded derive.staking.* derives, including addition of derive.staking.own*
Re-add fixed (with tests) checks for query args, previously disabled in 1.6.2
v1.6.2
Revert checks for query args, not working on .at() queries (proper fix in next version)
v1.6.1
Breaking changeapi.rpc.state.queryStorage(...) now fully decodes the Vec<StorageChangeSet> and returns a decoded [Hash, Codec[]][] when using this RPC.
StorageKey now has an .args property, decoded from meta where twox64_concat or blake128_concat are used on maps
Fix api.query.*.*.entries type conversions to return exact types (not Option in some cases)
Add api.query.*.*.keys to retrieve only the storage keys, similar to .entries
Full linked map retrievals will now use direct getStorage queries for faster operation
Underlying rpc-core interfaces now unwraps Error("...") when found in responses
Added derive.eras* interfaces for queries to new Substrate staking interfaces
Update derive.account to cater for new indices module storage (detected with fallbacks)
Adjust derive queries for session without module prefix (DoubleMap -> Map), detected on use
Add runtime validation for map arguments to api.query.*
TypeScript interfaces for linked maps now correctly generates as [Type, Linkage<Next>]
v1.5.1
Important Substrate master has updated staking, on older chains supply StakingLedger: 'StakingLedgerTo223'
Important Substrate master has updated collective, on older chains supply Votes: 'VotesTo230'
Add proper support for type generation with an Enum containing an Tuple (Thanks to https://github.com/monitz87)
Add types & metadata for the latest Polkadot/Substrate runtime versions (master branches)
Type extraction will now allow the same sub-module name across packages, i.e. @polkadot/types/interfaces/runtime & @mine/interfaces/runtime will be valid
Add .range([from, to]: [Hash, Hash?], ...args: any[]): [Hash, Codec][] on all storage entries
Add .raw(...args: any[]): Promise<Uint8Array & Codec> to all RPC calls, returning the un-encoded result
Allow pre-module type aliasing with typesAlias: { <moduleName>: { <meta-type>: <alias-type> } } in API construction options
Allow BTreeMap to be initialized with a Record<string, any> object (in addition to Map)
Allow for HashMap<KeyType, ValueType> definitions
Bool will now correctly return isEmpty on false/default values
Refresh the NetworkState types as returned by the rpc.system.networkState() call to current
Expose registry.createClass(<typeName>) to allow for creating type classes. If you are using createClass or ClassOf in your code, it is recommended to swap to this instance.
Add additional derives to api.derive.staking to handle lazy-payout retrievals
Update @polkadot/{util, util-crypto, keyring} to 1.6.1 & @polkadot/wasm to 1.2.1
1.4.1
Breaking change (TypeScript only) The *.d.ts files now contain TypeScript 3.8 features (specifically #private), which is not usable in TS versions < 3.8
Breaking change - api.derive.staking.* has updated result types and detects support for lazy payouts queries
Rework type generation for api.{query, tx} to properly handle complex type inputs (Thanks to https://github.com/monitz87)
Rework metadata --strict mode to effectively decorate chain metadata (Thanks to https://github.com/monitz87)
Important Current versions of Polkadot/Substrate have dropped support for linked maps on storage entries. If you are using these queries to retrieve all entries, for instance staking.{nominators,validators}() and using an upgraded chain, you need to swap to retrieving entries via .entries() or .keys() for the keys.
Pull in support and types for latest Polkadot/Substrate
Add support for the new Substrate state_getKeysPaged RPC, including use in storage keys
Move derive.staking.controllers to derive.staking.stashes, reflecting actual content
Cater for adjusted storage (non-linked mapped) for derive.staking.stashes queries (with old-compat)
Expanded derive.staking.* derives, including addition of derive.staking.own*
Re-add fixed (with tests) checks for query args, previously disabled in 1.6.2
1.6.2 Mar 12, 2020
Revert checks for query args, not working on .at() queries (proper fix in next version)
1.6.1 Mar 12, 2020
Breaking changeapi.rpc.state.queryStorage(...) now fully decodes the Vec<StorageChangeSet> and returns a decoded [Hash, Codec[]][] when using this RPC.
StorageKey now has an .args property, decoded from meta where twox64_concat or blake128_concat are used on maps
Fix api.query.*.*.entries type conversions to return exact types (not Option in some cases)
Add api.query.*.*.keys to retrieve only the storage keys, similar to .entries
Full linked map retrievals will now use direct getStorage queries for faster operation
Underlying rpc-core interfaces now unwraps Error("...") when found in responses
Added derive.eras* interfaces for queries to new Substrate staking interfaces
Update derive.account to cater for new indices module storage (detected with fallbacks)
Adjust derive queries for session without module prefix (DoubleMap -> Map), detected on use
Add runtime validation for map arguments to api.query.*
TypeScript interfaces for linked maps now correctly generates as [Type, Linkage<Next>]
1.5.1 Mar 06, 2020
Important Substrate master has updated staking, on older chains supply StakingLedger: 'StakingLedgerTo223'
Important Substrate master has updated collective, on older chains supply Votes: 'VotesTo230'
Add proper support for type generation with an Enum containing an Tuple (Thanks to https://github.com/monitz87)
Add types & metadata for the latest Polkadot/Substrate runtime versions (master branches)
Type extraction will now allow the same sub-module name across packages, i.e. @polkadot/types/interfaces/runtime & @mine/interfaces/runtime will be valid
Add .range([from, to]: [Hash, Hash?], ...args: any[]): [Hash, Codec][] on all storage entries
Add .raw(...args: any[]): Promise<Uint8Array & Codec> to all RPC calls, returning the un-encoded result
Allow pre-module type aliasing with typesAlias: { <moduleName>: { <meta-type>: <alias-type> } } in API construction options
Allow BTreeMap to be initialized with a Record<string, any> object (in addition to Map)
Allow for HashMap<KeyType, ValueType> definitions
Bool will now correctly return isEmpty on false/default values
Refresh the NetworkState types as returned by the rpc.system.networkState() call to current
Expose registry.createClass(<typeName>) to allow for creating type classes. If you are using createClass or ClassOf in your code, it is recommended to swap to this instance.
Add additional derives to api.derive.staking to handle lazy-payout retrievals
Update @polkadot/{util, util-crypto, keyring} to 1.6.1 & @polkadot/wasm to 1.2.1
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Bumps @polkadot/api from 1.0.1 to 1.7.1.
Release notes
Sourced from @polkadot/api's releases.
Changelog
Sourced from @polkadot/api's changelog.
Commits
623420c
[CI Skip] 1.7.19ea6053
1.7 (#2059)73dce6b
[CI Skip] 1.7.0-beta.195a7811c
Bump metadata (#2058)1c529bd
[CI Skip] 1.7.0-beta.183f4576f
Add yarn matrix (#2057)2619489
[CI Skip] 1.7.0-beta.17f165845
Collapse actions matrix (#2056)897f03e
[CI Skip] 1.7.0-beta.1682c1e3f
Cater for new non-linked map validator queries (#2055)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)