Bump @polkadot/api from 1.12.2 to 3.7.3 in /polkaviz-app

[dependabot-preview[bot]]

Bumps @polkadot/api from 1.12.2 to 3.7.3.

Release notes

Sourced from @polkadot/api's releases.

v3.7.3

Changes:

• Added Polkadot upgrade block for runtime 27 (known checkpoint optimization)

v3.7.2

Changes:

• Adjusted the Keys type for the 28 runtime on Kusama, Polkadot & Westend

v3.7.1

Upgrade priority: Low. However recommended for current Substrate master, Polkadot and Rococo users and those wishing to support the upcoming Polkadot 28 runtime with the new MultiAddress.

• Breaking change As indicated in the 3.5.1 release notes, the Address/LookupSource defaults have now been adjusted for MultiAddress. If your chain does not use these types, explicitly add the correct Address/LookupSource types. This new extensible format is mean to cater for all address types into the future, removing a lot of discrepancies between chains.

Contributed:

• Extraction of the block author on Moonbeam (Thanks to https://github.com/joelamouche)
• Cleanup logs with HTTP providers, no subs (Thanks to https://github.com/Tbaut)

Changes:

• Allow .slice operator on the Vec type
• Apply MultiAddress as a default
• Adds support for the upcoming Polkadot 28 and Kusama 2028 runtimes
• Add checkpoint for Kusama 2027 upgrade
• Update all parachain types (as per latest Rococo)
• Correctly use relay blockNumber in parachain validation data
• remove information log for capabilities detection (creates confusion)
• Remove explicit references to global, use the x-global detection
• Remove explicit module in package.json (exports map available)

v3.6.1

Upgrade priority: Medium if not already on at least 3.3.1. The next upgrade of Kusama/Polkadot requires it.

• Breaking change To support chains with multiple tokens, such as bridges, the ChainProperties type now returns an array of tokens and decimals (instead of singular values) in the token{Decimals, Symbol} getters. Additionally, this means that the registry interfaces has been changes, to registry.chainDecimals: number[] and registry.chainTokens: string[]. Where used the [0] index will return the first value if only interested in a single, for a straight conversion.

Changes:

• Allow for the detection of on-chain capabilities as available (e.g. AccountData, ValidatorPrefs)
• Cater for multiple tokens and decimals in the chain the chain system.properties (as per the chain specification)
• Add a instances: { [key]: [module1, module2] } definition in teh bundle types, allowing for multiple instances (e.g. Balances)
• Adjust the api-derive for balances to retrieve values via instances as well as across multiple modules
• Ensure all types are registered for all metadata typegen steps
• Add rpc.payment.queryFeeDetails RPC endpoint
• Update types & metadata to latest Substrate
• Move the @polkadot/x-rxjs package into the common repo
• Allow doc generation for errors/events (markdown outputs)

v3.5.1

... (truncated)

Changelog

Sourced from @polkadot/api's changelog.

3.7.3 Feb 2, 2021

Changes:

• Added Polkadot upgrade block for runtime 27 (known checkpoint optimization)

3.7.2 Feb 2, 2021

Changes:

• Adjusted the Keys type for the 28 runtime on Kusama, Polkadot & Westend

3.7.1 Feb 1, 2021

Upgrade priority: Low. However recommended for current Substrate master, Polkadot and Rococo users and those wishing to support the upcoming Polkadot 28 runtime with the new MultiAddress.

• Breaking change As indicated in the 3.5.1 release notes, the Address/LookupSource defaults have now been adjusted for MultiAddress. If your chain does not use these types, explicitly add the correct Address/LookupSource types. This new extensible format is mean to cater for all address types into the future, removing a lot of discrepancies between chains.

Contributed:

• Extraction of the block author on Moonbeam (Thanks to https://github.com/joelamouche)
• Cleanup logs with HTTP providers, no subs (Thanks to https://github.com/Tbaut)

Changes:

• Allow .slice operator on the Vec type
• Apply MultiAddress as a default
• Adds support for the upcoming Polkadot 28 and Kusama 2028 runtimes
• Add checkpoint for Kusama 2027 upgrade
• Update all parachain types (as per latest Rococo)
• Correctly use relay blockNumber in parachain validation data
• remove information log for capabilities detection (creates confusion)
• Remove explicit references to global, use the x-global detection
• Remove explicit module in package.json (exports map available)

3.6.1 Jan 24, 2020

Upgrade priority: Medium if not already on at least 3.3.1. The next upgrade of Kusama/Polkadot requires it.

• Breaking change To support chains with multiple tokens, such as bridges, the ChainProperties type now returns an array of tokens and decimals (instead of singular values) in the token{Decimals, Symbol} getters. Additionally, this means that the registry interfaces has been changes, to registry.chainDecimals: number[] and registry.chainTokens: string[]. Where used the [0] index will return the first value if only interested in a single, for a straight conversion.

Changes:

• Allow for the detection of on-chain capabilities as available (e.g. AccountData, ValidatorPrefs)
• Cater for multiple tokens and decimals in the chain the chain system.properties (as per the chain specification)
• Add a instances: { [key]: [module1, module2] } definition in teh bundle types, allowing for multiple instances (e.g. Balances)
• Adjust the api-derive for balances to retrieve values via instances as well as across multiple modules

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by polkadotjs, a new releaser for @polkadot/api since your current version.

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)

[dependabot-preview[bot]]

Superseded by #194.