Skip to content

Content Element Data Migration Strategy #591

@rkusan00

Description

@rkusan00
  • Ability to evolve element data over time
  • Support for automatic and manual (controlled by the user) change process
    • Sometimes we might not want to automatically migrate die to style change or require additional user input
  • Consider migrating to different content element types, not just evolving one element
  • This is what manifest version prop represent, it should be stored in element data

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions