Align communication and documentation of migrations #7477
Description
Our current migrations have various naming conventions and scopes (ex: from a single function to focusing on specific CSS properties). This might make it confusing as a 1P or 3P Shopify App developer as to which migrations to apply. We should standardize on a few details:
- How we name migrations
- How we categorize them
- How developers use them
These standards should be reflected in the Polaris documentation.
🔗 Proposed alignment of naming, scope, and structure
Other codemod references:
Metadata
Metadata
Assignees
Labels
No labels