What

Added a time tracking system for the fetching of updated tx data to account for rapid websocket events resulting in concurrent requests not always resolving in the right order

Why

to fix a bug

Testing done

tested the bug fix
frontend unit OK

Decisions made

Initially tried with a deboucing system but didn't manage to make it work, so switched to a timestamp tracking system
Allowed get transaction endpoint to return null if a tx doesn't exist

Checks

[x] I have tested this code
[x] I have reviewed my own PR
[x] I have created an issue for this PR
[x] I have set a descriptive PR title compliant with conventional commits

Reviewing tips

deploy contracts and fire write transactions; all the statuses should eventually properly end up in finalized state

User facing release notes

Fixed a bug where the statuses wouldn't update properly in the transaction list

codecov[bot] commented 1 week ago

Codecov Report

Attention: Patch coverage is 82.14286% with 5 lines in your changes missing coverage. Please review.

Project coverage is 18.81%. Comparing base (af6baf7) to head (897cd71).

Files with missing lines	Patch %	Lines
frontend/src/stores/transactions.ts	57.14%	3 Missing :warning:
frontend/src/hooks/useTransactionListener.ts	90.47%	2 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #618 +/- ## ========================================== + Coverage 18.61% 18.81% +0.20% ========================================== Files 123 123 Lines 9618 9638 +20 Branches 299 299 ========================================== + Hits 1790 1813 +23 + Misses 7744 7742 -2 + Partials 84 83 -1 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features: