Skip to content

Handle old dashboard configuration more gracefully #68

Open
@mtheoryx

Description

@mtheoryx

We've run into this issue a few times on stream, and I'm sure some of you also have run into it locally.

Currently, all the state is stored but sometimes can drift when new features come rolling in. It's quite frustrating that we don't have an upgrade path or at least a way to let the user know there is a conflict.

I'm opening this just to get a dialogue started and get some thoughts out there!

Here are some initial ideas:

  • A way to detect state drift
  • A way to alert users of a state drift problem, and optionally remediation for them?
  • Perhaps a second look at how we're storing state?

Toss in some other thoughts or ideas, we can do this together!

Cheers all! @mpaarating

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfeedback wantedRequest for community feedbackhelp wantedExtra attention is neededquestionFurther information is requested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions