Skip to content

Persist editor state #10

Description

@stuf

Plan support for persisting editor state in a suitable backend.

Ideas/thoughts/things:

  • maybe use a localStorage/sessionStorage-like API?
  • by default localStorage, but could be a custom back-end
  • use checkpoints/batches instead of updating instantly on state change

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestfutureFuture improvements

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions