chore: add skeleton to staking page #840
Conversation
🦋 Changeset detectedLatest commit: 7905e2c The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
5 Skipped Deployments
|
iamonuwa
requested review from
a team,
JulesFiliot,
felicio,
jinhojang6 and
jkbktl
* fix(release): scope remark linting to content directory only * chore(status.app): add changeset
JulesFiliot
left a comment
JulesFiliot
left a comment
There was a problem hiding this comment.
All good and nice 👍
Except the skeleton for the vault's table which is not displaying for some reason:
The loading state looks like that:
* Rename 'Mobile' to 'New mobile' in routes why - status-im/status-website#1620 (comment) * Rename 'Mobile' to 'New mobile' in routes
there is no loading state design for the table. at the moment, it looks like this 
|
…loading-to-staking
|
If I close Connect Wallet dialog via (X) close button, Stake page gets stuck on loading skeleton. |
* chore: fix vercel comments * feat: add Status Wallet detection and update SIWE message creation * chore: add changelog * chore: revert create message response
check again, please. |
* add withdraw * Add changeset for patch updates * address feedback * address feedback * change contracts address back to production * add use client to emergencyMode hook * test fix build * test fix build
JulesFiliot
left a comment
JulesFiliot
left a comment
There was a problem hiding this comment.
If not seeing the skeleton on the vaults' table is expected, all good ! 
| // Skeleton Component | ||
| // ============================================================================ | ||
|
|
||
| function VaultsTableSkeleton() { |
There was a problem hiding this comment.
I don't know if it's expected but I don't see the skeleton on the vaults' table. I see what you mentioned here
github-project-automation
bot
moved this from In Progress
to Waiting
in Web & User Interfaces
6 participants
closes #839