-
Notifications
You must be signed in to change notification settings - Fork 5
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
[mtg-836] Separate fungible token accounts from non-fungible ones #305
Conversation
…res for different types of assets
…ate-fungible-tokens-updates
079a666
to
0cf3ab9
Compare
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.
Let's catch up and sync on those 2 synchronizers running. The approach looks good, the separation should be thought through. I'd really love to merge this change asap
a8ccae6
to
0622c99
Compare
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.
As an idea (not a suggestion to implement right now) - wdyt of running 2 separate binaries - synchronizer_fungible, synchronizer_nft. Maybe it'll make separation easier. Or it could be a single binary with run mode - fungible/non-fungible
also renamed methods due to their different nature
&& updated tests && refacrored ASSET_TYPE constant
dcf47db
to
555d596
Compare
9f903ad
to
0746bc1
Compare
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.
I still need to go over the synchronizer
18d6a4a
to
f97a3e8
Compare
f97a3e8
to
08f705a
Compare
}; | ||
|
||
self.copy_fungibles(fungible_tokens_path, &mut transaction) | ||
.await?; |
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.
The explicit rollback will not be called here, if the copy_fungible errors, so we'll still rely on rust to rollback the 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.
Great job, thank you! Those transaction rollbacks should be called explicitely on any errors though
d5f3d6d
to
4a9b34f
Compare
No description provided.