Rails Admin State Machine

Properly manage state_machine states from rails_admin

Allows easily sending state_machine events to a model from Rails Admin, including support for ActiveRecord \ Mongoid and custom state field name and multiple state machines per model.

Differences between this and the main branch.

1. On the list view, the current state with coloration will be displayed. No events will be displayed here.
2. On the Edit view, there will be the event buttons as well as the current state. The enum view has been removed.
3. After clicking a state machine action, the user is redirected back to the show view. This allows for state-dependent editing.

Installing

Add this line to your application's Gemfile:

gem 'rails_admin_state'

And then execute:

$ bundle

Or install it yourself as:

$ gem install rails_admin_state

Usage

Add the state action:

RailsAdmin.config do |config|
  config.actions do
    ......
    state
  end
end

Mark the field you need display as state:

rails_admin do
  list do
    field :state, :state
    ...
  end
  edit do
    field :state, :state
    ...
  end
  ...
end

States and event button/label custom classes:

**NOTE: this is now required **

rails_admin do
  list do
    field :state, :state
    ...
  end
  ...
  state({
    events: {reject: 'btn-warning'}
    states: {on_moderation: 'btn-warning'}
  })
end

i18n (state and event names):

Just as usual for state_machine, see:

http://rdoc.info/github/pluginaweek/state_machine/master/StateMachine/Integrations/Mongoid

http://rdoc.info/github/pluginaweek/state_machine/master/StateMachine/Integrations/ActiveRecord

For namespaced models use "/", just as usual: "Blog::Post" is "blog/post"

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request