Skip to content

Model/process level states and engineering them, like AASM (ruby) #39

Description

@sanjarcode

Why + what?
Consider the example of an Ecommerce store, the general buy process has the following steps:
Place order -> Pay -> Dispatch -> *transition from warehouses -> arrive at local warehouse -> out for delivery -> delivered -> cancel/return? -> refund?

A lot is going on here. I have of courses omitted multiple possible states at each point.

Checkout:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions