Remove specName-specific warnings (#2781)

This commit is contained in:
Jaco Greeff
2020-10-25 14:45:13 +01:00
committed by GitHub
parent d4aa36981d
commit 1944ffe017
2 changed files with 0 additions and 20 deletions
-3
View File
@@ -12,7 +12,6 @@ import typesChain from './chain';
import typesModules from './modules';
import typesSpec from './spec';
import upgrades from './upgrades';
import warnings from './warnings';
// flatten a VersionedType[] into a Record<string, string>
/** @internal */
@@ -46,8 +45,6 @@ export function getSpecTypes ({ knownTypes }: Registry, chainName: Text | string
const _specName = specName.toString();
const _specVersion = bnToBn(specVersion).toNumber();
(warnings[_specName] || []).forEach((warning) => console.warn(`*** ${warning}`));
// The order here is always, based on -
// - spec then chain
// - typesBundle takes higher precedence
-17
View File
@@ -1,17 +0,0 @@
// Copyright 2017-2020 @polkadot/types-known authors & contributors
// SPDX-License-Identifier: Apache-2.0
// Type overrides for specific spec types & versions as given in runtimeVersion
const warnings: Record<string, string[]> = {
'node-template': [
'',
'You are using the node-template, depending on your config and age of the template, you may',
'have some unexpected results without applying the correct config for your node type:',
'',
'- If you have trouble sending txs, apply https://polkadot.js.org/docs/api/FAQ#i-cannot-send-transactions-from-my-node-template-based-chain',
'- If you have trouble parsing events, apply https://polkadot.js.org/docs/api/FAQ#using-a-non-current-master-node-i-have-issues-parsing-events',
''
]
};
export default warnings;