-
Notifications
You must be signed in to change notification settings - Fork 7
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
Restructure directories and contract content + README updates #52
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #52 +/- ##
==========================================
+ Coverage 82.88% 85.56% +2.67%
==========================================
Files 18 19 +1
Lines 818 859 +41
==========================================
+ Hits 678 735 +57
+ Misses 140 124 -16 ☔ View full report in Codecov by Sentry. |
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.
Looks good! Just a few small comments
Similarly, Cadence contracts can implement the [`IBridgePermissions.cdc` contract | ||
interface](./cadence/contracts/bridge/interfaces/IBridgePermissions.cdc). This contract has a single method | ||
`allowsBridging()` with a default implementation returning `false`. Again, the bridge explicitly checks for the | ||
implementation of `IBridgePermissions` and the value of `allowsBridging()` to validate that the contract has not opted | ||
out of bridging. Should you later choose to enable bridging, you can simply override the default implementation and | ||
return true. |
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.
It would be good to get this added to the V2 standards so we can show that every NFT contract needs to be cognizant about if they want to allow bridging or not. Can you make a PR to the v2 standard branch?
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.
Definitely, I can follow up with a PR early next week
Co-authored-by: Joshua Hannan <[email protected]>
f936101
to
d0a2a0d
Compare
Co-authored-by: Joshua Hannan <[email protected]>
Closes: #29 #47 #49 #50
Stacked on: #48
Description
For contributor use:
master
branchFiles changed
in the Github PR explorer