SGiaccobasso commented 3 months ago

Description

Recover the deployment message id when visiting the token details page if missing.

⛑️ What was done:

Create query to recover message id by token id.
Check if the id is missing in every visit to token details page and try to recover it.

Type of change

Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Ready to merge

🧪 How to test:

Go to the details page of a token with a missing deployment message it, check it shows as unregistered ITS token and wait for it to update. You can achieve this by deleting the message id from the db for an existing token.

🗒️ Notes:

[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have commented my code, particularly in hard-to-understand areas
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

🖼️ Recording:

https://github.com/user-attachments/assets/25b9ca33-fe5d-4d00-96ab-a21cfb2f6225

Check how the token with the missing deployment message id updates automatically in the details page after some seconds.

vercel[bot] commented 3 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
axelar-maestro	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 29, 2024 4:35pm
axelar-registry	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 29, 2024 4:35pm
axelar-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 29, 2024 4:35pm