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.
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
Cadence Account Storage Map Migration #6761
base: auto-update-onflow-cadence-v1.3.0
Are you sure you want to change the base?
Cadence Account Storage Map Migration #6761
Changes from all commits
5c65c32
e7d04a4
95ca4de
8e6fbbf
de4b564
f611094
c75d4fc
b31696c
0906f96
2a04742
5794140
b1c86c5
06420d1
0a393ef
2b1ecac
a1ca332
8b597cb
f86dd29
814c47a
e910cd0
a57912f
d24f07e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This is really small, but the batching logic could probably live in the
Migration
contract instead of in the V2 oneThere 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.
See #6761 (comment): The idea is that all logic related to the particular migration, the "account v2 migration", lives in
AccountV2Migration
, andMigration
only delegates.If we add the logic of the "account v2 migration" to the
Migration
contract, we won't be able to reuse it for other purposes, as the contract update rules e.g. don't allow removing enums, etc.