The error from useWeb3Context is of type Error, which doesn't have a code property - leads to TypeScript warning about web3-react HOT 7 CLOSED

hey @pcowgill, thanks for the report!

makes sense, i override that error locally with this snippet: https://github.com/NoahZinsmeister/web3-react/blob/latest/src/declarations.ts#L20. looking at MDN though, it seems like name might be the right property for what i'm trying to accomplish: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/name.

i'm going to keep the issue open and experiment with this in the next version.

from web3-react.

🙏 that sounds perfect, i'll try that!

from web3-react.

going to close this, as v6 uses custom errors which can be checked with instanceof! thanks for bringing this up.

from web3-react.

@NoahZinsmeister Thanks for the example of how to override it! Agreed, I think name would suit your needs here.

from web3-react.

Also, you can subclass errors so that they’ll have name set automatically in the case of a frequently used “error code”

from web3-react.

@NoahZinsmeister In the meantime, do you know of any examples of an app using this library making use of those or similar declarations? Thanks!

from web3-react.

This seems to work for an app using this lib:

ErrorWithCode.ts

export interface ErrorWithCode extends Error {
  code?: string | number | undefined;
}

MyComponent.tsx

import { ErrorWithCode } from "[insert-path-here]/types/ErrorWithCode";
const {
    active,
    error,
    setConnector,
    setError
  }: {
    active: boolean;
    error?: ErrorWithCode | null;
    setConnector: any;
    setError: any;
  } = useWeb3Context();

(The any type for the functions isn't good TypeScript, but left it like that since that's not the focus here.)

from web3-react.