-
Notifications
You must be signed in to change notification settings - Fork 13
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
Pricing Module and Cleanup (WIP) #189
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
||
assert!(payment.value() == price, EIncorrectAmount); | ||
assert!(coin::value(&payment) == price, EIncorrectAmount); |
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.
why move away from receiver syntax??
/// Checks if `parent` domain is a valid parent for `child`. | ||
public fun is_parent_of(parent: &Domain, child: &Domain): bool { | ||
number_of_levels(parent) < number_of_levels(child) && | ||
number_of_levels(parent) < number_of_levels(child) && |
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.
number_of_levels(parent) < number_of_levels(child) && | |
parent.number_of_levels() < child.number_of_levels() && |
/// Checks if `parent` domain is a valid parent for `child`. | ||
public fun is_parent_of(parent: &Domain, child: &Domain): bool { | ||
number_of_levels(parent) < number_of_levels(child) && | ||
number_of_levels(parent) < number_of_levels(child) && | ||
&parent(child).labels == &parent.labels |
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.
&parent(child).labels == &parent.labels | |
child.parent().labels == &parent.labels |
packages/renewal/sources/renew.move
Outdated
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.
We can re-deploy this package and deauthorize the old / authorize the new. We can avoid the V2 structs that way.
No description provided.