Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Enumify adds an enum command to all ActiveRecord models which enables you to work with string attributes as if they were enums
branch: master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.

Enumify Build Status

Enumify adds an enum command to all ActiveRecord models which enables you to work with string attributes as if they were enums


Just add the enumify gem to your GemFile

gem 'enumify'

How to use

Just call the enum function in any ActiveRecord object, the function accepts the field name as the first variable and the possible values as an array

class Event < ActiveRecord::Base
    enum :status, [:available, :canceled, :completed]

Rails 4.1+

You can also instantiate a Enumify enum by calling the enumify method instead of enum.
This is especially helpful when your app is running Rail 4.1 or better which has it's own built in enum (although not as good)

class Event < ActiveRecord::Base
    enumify :status, [:available, :canceled, :completed]


After that you get several autogenerated commands to use with the enum

# Access through field name

event.status                # returns the enum's current value as a symbol
event.status = :canceled    # sets the enum's value to canceled (can also get a string)

# Shorthand methods, access through the possible values

event.available?            # returns true if enum's current status is available
event.canceled!             # changes the enum's value to canceled

# Get all the possible values

Event::STATUSES             # returns all available status of the enum



By default the enum field does not support a nil value. In order to allow nil values add the allow_nil option (similar to the Rails validation option).

class Event < ActiveRecord::Base
    enum :status, [:available, :canceled, :completed], :allow_nil => true

Event.create! # Is valid and does not throw an exception.


By default all enum values are available as scopes, bang and query methods based on the value. You can add a prefix for the enum values in order to differentiate different enums on the same object.

class Event < ActiveRecord::Base
    enum :status, [:available, :canceled, :completed], :prefix => true
    enum :subtype, [:company, :personal], :prefix => 'type'

event.available?            # Not available anymore
event.status_available?     # when prefix true
event.type_company?         # you can set a specific name for your prefix


Another cool feature of enumify is the option to add a callback function that will be called each time the value of the field changes This is cool to do stuff like log stuff or create behaviour on state changes

All you need to do is add a x_changed method in your class and the enumify will call it

class Event < ActiveRecord::Base
    enum :status, [:available, :canceled, :completed]

    def status_changed(old, new)
        puts "status changed from #{old} to #{new}"


One last thing that the enumify gem does is created scope (formerly nested_scopes) so you can easly query by the enum

For example if you want to count all the events that are canceled you can just run


In addition you can also use a negation scope to retrieve all the records that are not set to the given value. For example to count all the events that are not canceled you can run


Copyright (c) 2011 Yonatan Bergman, released under the MIT license

Something went wrong with that request. Please try again.