-
Notifications
You must be signed in to change notification settings - Fork 138
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
Handle unmigrated path capabilities and path links in Account.capabilities functions #3562
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:master commit e70d1be Collapsed results for better readability
|
SupunS
approved these changes
Aug 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Path links which cannot be migrated stay as-is (see
LinkValueMigration.Migrate
, whengetPathCapabilityFinalTarget
returns failure). Path capabilities which cannot be migrated stay as-is (seeCapabilityValueMigration.migratePathCapabilityValue
, when controller ID is missing from mapping).As result, we cannot assume capability values in general and values stored in public paths are always ID capability values (
IDCapabilityValue
), they might be path capability values (PathCapabilityValue
) and path link values (PathLinkValue
).Add a
CapabilityValue.Address()
function to easily get the address ofIDCapabilityValue
andPathCapabilityValue
.I didn't do this for the
Type
andID
fields, because I realized it would require a lot more code to change. It still would be nice to also add getter functions for those fields, in a follow up PR, laterFix the export of path capability values. They don't always have a borrow type.
I noticed this when writing the tests, as publishing a capability emits an event which includes the capability, which leads to an export of the event and the capability it contains.
Handle path capability values and path link values in
Account.capabilities.get
,publish
, andunpublish
master
branchFiles changed
in the Github PR explorer