Fix provider recursion bug, provider function types #5829
Merged
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.
Fixes APP-1567
What changed (plus any additional context for devs)
getProviderForNetwork
was being repeatedly called throughout the app, for every network, due to thegetProvider
function within the network objects being invoked any timegetNetworkObj
orgetXNetworkObj
was invokedgetProviderForNetwork
was called for a not-yet-cached network, the calling ofgetNetworkObj
from withingetProviderForNetwork
would then again callgetProviderForNetwork
due togetProvider
within the network object being invoked, leading to a recursive loop that would run until the provider eventually made it into the cachegetProviderForNetwork
andgetCachedProviderForNetwork
functionsgetIsHardhatConnected
helper functionScreen recordings / screenshots
What to test