Skip to content

Saving bug #166

Description

@GabPSS

PR #164 introduced a saving issue
When saving, a future error is thrown because it's returning a future inside a setState.
Save function needs to be rewritten to accommodate for this issue
Note that it doesn't actually affect saving, but there could be some issue there.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions