Added ability to close transaction toasts on timeout #1352
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
|
|
||
| return () => { | ||
| if (lifetimeRef.current) { | ||
| clearTimeout(lifetimeRef.current); |
There was a problem hiding this comment.
I think would be more correct to check the transaction on the server then close it instead of closing it by force
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.
Issue
Transaction toasts remain in infinite pending sometimes
Root cause
Websocket event is not triggered or API fails
Fix
Add a transaction toast max lifetime timer that sets the toast as timed out after specific time
Additional changes
Improved websocket connection events handling
Contains breaking changes
Updated CHANGELOG
Testing