fix: false positive for warnProvider message #232
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
simboonlong
approved these changes
Jul 28, 2022
|
🎉 This PR is included in version 7.10.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As suggested, I was trying to setup my own version of the oa-verify api. I'm trying to target the Goerli test network, since Ropsten and Rinkeby will become deprecated in the future. (See this for more info).
I did come across the same issue as @HJunyuan described here. I looked at the logic of the code and I think just removing the warning message will fix the false positive. Feel free to correct/comment if removing this line has any other side effects for the package! 😄
Fixes #223