List all possible states an object can have

[troessner]

Concrete use case:

Admin interface: List all possible state names an object can have.

Right now this is only possible like this:

Order.state_machines.first[1].states.map(&:name)

which is obscure and counter intuitive.

We need something which is intuitive and easily accessible a la:

Order.possible_states

which the first state machine being the default argument or something like that.

I'll look into this as soon as possible.

[qoobaa]

Seems good. Is there a possibility to have multiple machines in the same model? If there is, you need to provide multiple "possible_states" methods.

BTW: add yourself to README/LICENSE files. You're the current maintainer of the gem, aren't you? You can also move the repository to your github account if you wish.

[troessner]

Seems good. Is there a possibility to have multiple machines in the same model? If there is, you need to provide multiple "possible_states" methods.

-> Ack.

You can also move the repository to your github account if you wish.

You're right, this would make sense, will do so later.

[troessner]

@qoobaa you would need to transfer ownership for this repository to my account since I can't do that myself, then I'll update licence, contact details etc.

[qoobaa]

To transfer this repo to another user, please contact support. 

I'll do it later. You can always create a fork or something.

[troessner]

I'll do it later.

Great, thanks!

[elskwid]

@troessner, I have a module I use that does something similar:

def state_names
  state_machines[:default].states.map(&:name)
end

I have been thinking about the multiple state machines per model/class. Currently, the ActiveRecord Module would break under these circumstances as it only ever writes to a field named :state - I've got some thoughts on this, perhaps a new issue?

[troessner]

@elskwid

Currently, the ActiveRecord Module would break under these circumstances as it only ever writes to a field named :state

Very good point.

I've got some thoughts on this, perhaps a new issue?

Yes, please create a new issue.

Actually, I can't think of a "real life" use case for multiple state machines.
If one really needs multiple state machines for one model this seems like a strong indicator that he actually needs two different models, not two different state machines.

[qoobaa]

If one really needs multiple state machines for one model this seems like a strong indicator that he actually needs two different models, not two different state machines.

Take a look at https://github.com/qoobaa/pioneers/blob/master/app/models/game.rb and try to merge those machines, or create a separate model :-).

[troessner]

@qoobaa hmm, I see. Well, at least now I know a real life example...:-)

[qoobaa]

From: Petros Amiridis (GitHub Staff)
Subject: [Contact] Transfer repo: qoobaa/transitions

I am afraid troessner/transitions already exists

Can you delete your fork? Then I'll try to transfer the repo again.

[troessner]

Done...:-)

[troessner]

3c5cb9d
-> Closed.