Tighten up loading indication logic#10103
Merged
Conversation
Contributor
|
Trying to figure out the e2e failure, but I'm also seeing this: |
Collaborator
Builds ready [bccba6b]
Page Load Metrics (548 ± 47 ms)
|
darkwing
previously approved these changes
Dec 17, 2020
Collaborator
Builds ready [c26e0be]
Page Load Metrics (516 ± 48 ms)
|
Gudahtt
reviewed
Dec 18, 2020
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Ensures that
hideLoadingIndicationis always called in all actions that callshowLoadingIndication. It's unclear how many of these actions were failing to hide the loading indication, because other actions supersethideLoadingIndication.At the very least,
updateTransactionwas probably failing to hide the loading indication in the error case.This PR also refactors a lot of actions to call
hideLoadingIndicationonce infinallyblocks as opposed to multiple times acrosstryandcatchblocks. We avoided making changes to functions usingPromisemethods, becausePromise.finallyis not supported by Waterfox, and it's not properly transpiled by Babel.