Closed jonator closed 2 weeks ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
osmosis-frontend | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Sep 19, 2024 1:04am |
The changes introduce a new interface, SkipStatusProvider
, which includes methods for tracking and retrieving transaction statuses. The SkipTransferStatusProvider
class is modified to use this interface instead of directly depending on SkipApiClient
. This enhances the modularity and error handling of transaction status retrieval. Additionally, the overall structure of the polling function is maintained while improving the separation of concerns within the codebase.
Files | Change Summary |
---|---|
packages/bridge/src/skip/transfer-status.ts |
Introduced SkipStatusProvider interface with methods for tracking and retrieving transaction status. Modified SkipTransferStatusProvider to accept SkipStatusProvider in its constructor, enhancing error handling and modularity. |
SkipApiClient
, which is directly related to the main PR's updates to the SkipApiClient
class, specifically the introduction of the apiKey
property.
What is the purpose of the change:
Linear Task
This PR refactors the Skip TransferStatusProvider to dep-inject the tx status and track endpoints so that we can create serverless functions that utilize the credentialed SkipApiClient on the server.
Also, I refactored the trackTransaction POST call to skip to be within a catch clause instead of a try catch statement. This makes it slightly more readable as there's less jumping around when interpreting the logic related to prompting Skip to track transactions before continuing the polling.
Brief Changelog
Testing and Verifying
Tested locally with Skip transfers in the deposit/withdraw flow, verifying that conclusive statuses can be received from Skip.