Skip to content

(Prompt to?) absorb new server state into client upon Save #21

@issa-tseng

Description

@issa-tseng

Broken out from #19: if the server sends a data payload back to the client upon save, we should use that as the new client state. But perhaps we should ask the user first? (And/or we need to disable the entire interface while a save is transacting?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions