Don't log full error (#2952)
* Don't log full error In `txwrapper` we can't always know if a payload is a signing payload or a signed tx so we first try one and then the other. When the former fails users get a scary-looking error. If upstream logs the error there's little we can do about it lest we [monkey patch `console.error`](https://github.com/paritytech/txwrapper-core/pull/22/files#diff-ea2d1c5845dd0e2fb9814e98a3464c2c63a43922983391e98fe9c20c328e979cR55) which is nasty af. Hence this PR that removes the log here so that downstream can choose what to do with the error message. * Add UnsafeOptions to let callers decide if they want errors logged or not * Update packages/api-contract/src/util.ts Co-authored-by: Jaco Greeff <jacogr@gmail.com> * Update packages/rpc-core/src/index.ts Co-authored-by: Jaco Greeff <jacogr@gmail.com> * Update packages/rpc-core/src/index.ts Co-authored-by: Jaco Greeff <jacogr@gmail.com> * Update packages/types/src/create/createType.ts Co-authored-by: Jaco Greeff <jacogr@gmail.com> Co-authored-by: Jaco Greeff <jacogr@gmail.com>
This commit is contained in:
@@ -17,7 +17,7 @@ type ContractEvents = 'CodeStored' | 'ContractExecution' | 'Instantiated';
|
||||
type TOptions = BlueprintOptions | ContractOptions;
|
||||
|
||||
export function formatData (registry: Registry, data: Raw, { type }: TypeDef): Codec {
|
||||
return createTypeUnsafe(registry, type, [data], true);
|
||||
return createTypeUnsafe(registry, type, [data], { isPedantic: true });
|
||||
}
|
||||
|
||||
export function applyOnEvent <T> (result: SubmittableResult, type: ContractEvents, fn: (records: EventRecord[]) => T): T | undefined {
|
||||
|
||||
Reference in New Issue
Block a user