-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add TanStack Query to cache api response #277
Labels
🎨 dApp
dApp
Comments
@kkosiorowska was it handled in #520? |
Not exactly. But I think we leave this task. #520 has implemented TanStack Query for the few queries needed. But we don't use it everywhere. We'd probably want to review the already-implemented queries and switch to the TanStack where we can. |
r-czajkowski
added a commit
that referenced
this issue
Nov 7, 2024
Ref #811 Ref #277 Closes #814 Closes #813 This PR updates screens for deposit and withdrawal flows. The "Skeleton" loading screen from both Deposit and Withdraw flows is no longer needed. The new flow adds two steps: - "Opening your wallet for signature" Screen - "Awaiting Transaction" Screen Flow: 1. User initiates deposit: After pressing the Deposit/Withdraw CTAs, the user first sees the “Opening your wallet for signature” screen 2. Display wallet modal 3. Transition to ‘Awaiting Transaction’: Once the wallet modal is prompted, switch to the “Awaiting Transaction” screen while the user completes the signature. 4. Return to dapp: After signing with the wallet, the user returns to your dapp, where the “Awaiting Transaction” screen remains visible as needed. 5. Confirm deposit/withdraw: Once transaction is complete, display the “Deposit received” or "Withdrawal inititated" screens to confirm completion. https://github.com/user-attachments/assets/899263a7-0895-48ba-881e-c61b70e4c32d
nkuba
changed the title
Add TanStack Query to cache api resposne
Add TanStack Query to cache api response
Nov 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally mentioned by @r-czajkowski : #245 (comment)
The text was updated successfully, but these errors were encountered: