migrations guidelines #96
Conversation
There was a problem hiding this comment.
As discussed, here are some individual suggestions (one for each section) to improve the format (not changing the meaning at all):
- formatting (mostly making it bullet point lists)
- reverting the sentences by putting the action the dev has to do first then how and why doing it.
…uidelines md file
…d only with important notes for the migration process in general
…what state integrety checks section was saying
|
Hey @Gudahtt Thanks for the review!! |
Co-authored-by: Cal Leung <[email protected]>
Co-authored-by: Cal Leung <[email protected]>
Co-authored-by: Cal Leung <[email protected]>
|
Apologies if this is already a thing, but is there a way to export state logs in the mobile app? In Extension, you can do this in |
| - Always return the state at the end of the migration function, whether it was modified or not, | ||
| - Returning the state ensures that the migration process completes and the state is passed to the next migrations. | ||
|
|
||
| ## Testing Guidelines |
There was a problem hiding this comment.
Should we add something to look at the oldest widely adopted version to generate the first set of state for testing?
|
No description provided.