Sha256: faa0eb48622034d6050dd065a14f250e7d62604f05e2e333ab4e660e1246ef39

Contents?: true

Size: 1.09 KB

Versions: 7

Compression:

Stored size: 1.09 KB

Contents

TODO
====

* Take a look at using DataMapper's Enum type.
  - Does the Enum type support for all databases?  (SQLite?)


* I am not real happy with spec/unit/dsl:
  - The specs are brittle.
  - The specs don't actually test much.

  However, the integration specs are pretty thorough.  Maybe each
  serves their own purpose.


API QUESTIONS
=============

* Some people are asking for convenience methods.

  For example, instead of:
    light = TrafficLight.new
    light.color == "yellow"

  We could possibly offer:
    light.yellow?

  Advantages:
    - More compact syntax.

  Disadvantages:
    - Namespace pollution
    - Possible namespace collision if you have more than one state machine
      in your model.


* Should skipping to a new state automatically trigger the :enter event?


* Should we add loopback checking?

  In other words, if there is a transition defined from one state back to
  the same state, should the :enter and :exit events fire?


* Should we add support for DataMapper callbacks? (e.g. after saving)


SOMEDAY / MAYBE
===============

* Consider trying out a nested state machine.

Version data entries

7 entries across 7 versions & 1 rubygems

Version Path
dm-is-state_machine-0.10.1 TODO
dm-is-state_machine-0.10.0 TODO
dm-is-state_machine-0.9.7 TODO
dm-is-state_machine-0.9.10 TODO
dm-is-state_machine-0.9.11 TODO
dm-is-state_machine-0.9.8 TODO
dm-is-state_machine-0.9.9 TODO