-
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
fix: ocelloids upgrade #258
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✨✨🧹🧹🧹
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice 🧹
): boolean => { | ||
return transfer.token.id === Polkadot.DOT.id && isParachainToParachain(transfer) | ||
enum xcmNotificationType { | ||
Sent = 'xcm.sent', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question that I might answer myself later but that the introduction of this new enum interfere with old data on storage? I guess it doesn't matter as much since it's just about an ongoing tx.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, the reason is the xcmNotificationType
enum has been removed in Ocelloids SDK v2.4.x.
I created this enum to avoid checking many times on the notification type since it is not typed anymore by Ocelloids.
We never store this data, so no way to interfere with storage 🙂
It contains Ocelloids last version which fixes unsupported and missing tracking paths:
And includes: