Skip to content

Logic of SAVE progress seems wield #2

@Stupidism

Description

@Stupidism

Use Case

I wanted to add a middleware to modify payload to sync into storage-engine, but failed all the time.

Problem

Turnen out newState is saved into storage-engine before its action dispatched.

I think the right order should be:

  1. dispatch this SAVE action
  2. save into storage-engine in reducer or middleware.

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