feat: add account data revalidation after undelegation #488
Conversation
Enhances the Undelegate component by introducing a revalidation mechanism for account data using SWR. After a successful undelegation, the account data is refreshed after a 15-second delay to ensure the UI reflects the latest state.
|
Continuation of #481, which was accidentally closed. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…fallback - Removed unused SWR configuration in Undelegate component. - Updated AccountLayout to fetch fresh account data client-side, prioritizing it over static props. - Adjusted logic to ensure the UI reflects the latest account state by using the newly fetched data for various components.
|
@ECWireless decided to go with a hybrid approach where the static data fetched on build time is used as a fallback for client side fetched data. Seems to solve the problem quite efficiently as polling starts working again, so I expect this fixes other issues with static data in the website as well. |
|
Closes #192 |
|
@ECWireless only issue now is that we are getting a EDIT: Doesn't seem to resolve the issue. Could it be that the preview deployment API key has a lower rate limit than the production one? |
Jipperism
force-pushed
the
bugfix/192-no-option-to-redelegate-LPT-after-undelegating
branch
from
a18ab92 to
82bcaa4
Compare
ECWireless
deleted the
bugfix/192-no-option-to-redelegate-LPT-after-undelegating
branch
Enhances the Undelegate component by introducing a revalidation mechanism for account data using SWR. After a successful undelegation, the account data is refreshed after a 15-second delay to ensure the UI reflects the latest state.