Ability to set state column name about transitions

[troessner]

Mike,

I agree. I'm going to on holidays soon for a few weeks, so I won't be able to look into this any time soon.

Would you like to contribute to transitions? If yes, I'd add you as a contributor to this repository.

[mperham]

Thanks but I don't have time to work on a feature this big. It's ok, I just didn't add a state machine to that model and instead track state manually. Enjoy your vacation!

[troessner]

Thanks!
Gonna look into this issue afterwards..:-)

[christhekeele]

Correct me if I'm wrong, but with this feature, transitions would be able to support multiple states on the same Model, correct?

[troessner]

@christhekeele not really because there is only one state machine per model possible (you can define multiple state machine but this won't work as would expect).

[troessner]

Oh, actually that's a good point, I really should make that clear in the documentation, thanks for bringing that up..:)

[troessner]

This should make it more clear: 5cd28cd

[troessner]

FYI the ability to set state column name is still on my "should be implemented" list - I just haven't found the time to do so..:)

[christhekeele]

I forked it and poked around a little, but my ruby metaclassing capabilities aren't up to snuff. I'm using the state_machine gem for now (sadly, your DSL syntax is much more elegant) and may poke around its internals eventually.

[troessner]

In master -> closed.