We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Even after specifying a custom provider and resolver, the warnProvider message still appears.
warnProvider
Example code:
import { providers } from "ethers"; import { verificationBuilder, createResolver, openAttestationVerifiers } from "@govtechsg/oa-verify"; const NETWORK_NAME = "homestead"; const INFURA_API_KEY = "ENTER_KEY_HERE"; const verify = verificationBuilder(openAttestationVerifiers, { provider: new providers.InfuraProvider(NETWORK_NAME, INFURA_API_KEY), resolver: INFURA_API_KEY ? createResolver({ ethrResolverConfig: { networks: [{ name: "mainnet", rpcUrl: `https://mainnet.infura.io/v3/${INFURA_API_KEY}` }], }, }) : undefined, });
Warning message triggered from:
oa-verify/src/common/utils.ts
Lines 66 to 68 in b0fb5f4
The text was updated successfully, but these errors were encountered:
🎉 This issue has been resolved in version 7.10.1 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Even after specifying a custom provider and resolver, the
warnProvider
message still appears.Example code:
Warning message triggered from:
oa-verify/src/common/utils.ts
Lines 66 to 68 in b0fb5f4
The text was updated successfully, but these errors were encountered: