power_enum 1.3.3 → 1.3.4

data.tar.gz.sig

@@ -1 +1,2 @@
-��<��ߣ�S?x�y+m,~k�����NœZ���tV�u�Ɯ�<˛h����>gAˀ�zn}]
AZP[|\{q�|���h�eS� ��ׇ��W`��:[ߚ�M2��dJf颍���
k�tJ�����}��~��KU�z`v��}6��O,�u��q����(�G��`|ƭ��M���8��7��'�䫋.қ��>���b���E���1�hd��6ɷ��ߙ���Q��5/[�1|��$�#H��2�7"{$�t�띧
+��G��p��0k���3s�1Y;&�N�5ߘq���
+����k�*��Z`{��s	�POC�޵F�L�Sq2��f�5��q��B�"R,�CZ�,�=H>�I]T��z��v�2�'zo:�/_�|��W<�z���ғ0VN��������jNW�ܓx�n�����h��q����.*�@u��^0�֠��B{�*8jA�,l,jhP��2<��L�

data/README.markdown

@@ -7,8 +7,13 @@ https://github.com/albertosaurus/power_enum
 
 Enumerations for Rails 3.1/3.2 Done Right.
 
+## Versions
+
+* PowerEnum 1.X  (this version) supports Rails 3.1/3.2.
+* PowerEnum 2.X supports Rails 4, available here: https://github.com/albertosaurus/power_enum_2
+
 NOTICE: Version 1.0 removes support from Rails 3.0, as that version of Rails has no longer been supported for
-some time.  The last version to support Rails 3.0 was 0.11.1.
+some time. The last version to support Rails 3.0 was 0.11.1.
 
 ## What is this?:
 
@@ -18,7 +23,7 @@ It is particularly suitable for scenarios where your Rails application is not th
 when it's used for analytics or reporting.
 
 Power Enum is a fork of the Rails 3 modernization made by the fine folks at Protocool
-https://github.com/protocool/enumerations_mixin to the original plugin by Trevor Squires.  While many of the core ideas
+https://github.com/protocool/enumerations_mixin to the original plugin by Trevor Squires. While many of the core ideas
 remain, it has been reworked and a full test suite written to facilitate further development.
 
 At it's most basic level, it allows you to say things along the lines of:
@@ -52,8 +57,8 @@ See "How to use it" below for more information.
 
 ### READ THIS FIRST
 
-Starting with version 1.1.0, the gem is signed.  The public key is available
-here: https://github.com/albertosaurus/power_enum (look for gem-public\_cert.pem).  Hence, if
+Starting with version 1.1.0, the gem is signed. The public key is available
+here: https://github.com/albertosaurus/power_enum (look for gem-public\_cert.pem). Hence, if
 you can get an error like the following if you're installing in `HighSecurity` mode.
 
 ```
@@ -62,7 +67,7 @@ ERROR:  While executing gem ... (RuntimeError)
 ```
 
 If this happens, you need to add the PowerEnum public cert to your gem cert
-store.  Download the certificate (gem-public\_cert.pem) and run the following.
+store. Download the certificate (gem-public\_cert.pem) and run the following.
 
     gem cert -a gem-public_cert.pem
 
@@ -97,9 +102,9 @@ This package adds:
 
 `acts_as_enumerated` provides capabilities to treat your model and its records as an enumeration.
 At a minimum, the database table for an acts\_as\_enumerated must contain an 'id' column and a column
-to hold the value of the enum ('name' by default).  It is strongly recommended that there be
-a NOT NULL constraint on the 'name' column.  All instances for the `acts_as_enumerated` model
-are cached in memory.  If the table has an 'active' column, the value of that attribute
+to hold the value of the enum ('name' by default). It is strongly recommended that there be
+a NOT NULL constraint on the 'name' column. All instances for the `acts_as_enumerated` model
+are cached in memory. If the table has an 'active' column, the value of that attribute
 will be used to determine which enum instances are active.
 Otherwise, all values are considered active.
 
@@ -128,9 +133,9 @@ You should see output similar to this:
     invoke  test_unit
     create    test/unit/booking_status_test.rb
 
-That's all you need to get started.  In many cases, no further work on the enum is necessary.  You can run `rails generate enum --help`
-to see a description of the generator options.  Notice, that while a unit test is generated by default, a fixture isn't.  That is because
-fixtures are not an ideal way to test acts\_as\_enumerated models.  I generally prefer having a hook to seed the database from seeds.rb
+That's all you need to get started. In many cases, no further work on the enum is necessary. You can run `rails generate enum --help`
+to see a description of the generator options. Notice, that while a unit test is generated by default, a fixture isn't. That is because
+fixtures are not an ideal way to test acts\_as\_enumerated models. I generally prefer having a hook to seed the database from seeds.rb
 from a pre-test Rake task.
 
 ### migration
@@ -189,13 +194,13 @@ There are two methods added to Rails migrations:
 
 ##### create\_enum(enum\_name, options = {}, &block)
 
-Creates a new enum table.  `enum_name` will be automatically pluralized.  The following options are supported:
+Creates a new enum table. `enum_name` will be automatically pluralized. The following options are supported:
 
-- [:name\_column]  Specify the column name for name of the enum.  By default it's :name.  This can be a String or a Symbol
+- [:name\_column]  Specify the column name for name of the enum. By default it's :name. This can be a String or a Symbol
 - [:description]  Set this to `true` to have a 'description' column generated.
 - [:name\_limit]  Set this define the limit of the name column.
 - [:desc\_limit]  Set this to define the limit of the description column
-- [:active]  Set this to `true` to have a boolean 'active' column generated.  The 'active' column will have the options of NOT NULL and DEFAULT TRUE.
+- [:active]  Set this to `true` to have a boolean 'active' column generated. The 'active' column will have the options of NOT NULL and DEFAULT TRUE.
 - [:timestamps]  Set this to `true` to have the timestamp columns (created\_at and updated\_at) generated
 
 You can also pass in a block that takes a table object as an argument, like `create_table`.
@@ -261,7 +266,7 @@ Notice that a unique index is automatically created on the specified name column
 
 ##### remove\_enum(enum\_name)
 
-Drops the enum table.  `enum_name` will be automatically pluralized.
+Drops the enum table. `enum_name` will be automatically pluralized.
 
 Example:
 
@@ -295,29 +300,29 @@ With that, your BookingStatus class will have the following methods defined:
 
 ##### [](*args)
 
-`BookingStatus[arg]` performs a lookup for the BookingStatus instance for the given arg.  The arg value can be a
-'string' or a :symbol, in which case the lookup will be against the BookingStatus.name field.  Alternatively arg can be
-a Fixnum, in which case the lookup will be against the BookingStatus.id field.  Since version 0.5.3, it returns the arg
+`BookingStatus[arg]` performs a lookup for the BookingStatus instance for the given arg. The arg value can be a
+'string' or a :symbol, in which case the lookup will be against the BookingStatus.name field. Alternatively arg can be
+a Fixnum, in which case the lookup will be against the BookingStatus.id field. Since version 0.5.3, it returns the arg
 if arg is an instance of the enum (in this case BookingStatus) as a convenience.
 
 The `:on_lookup_failure` option specifies the name of a *class* method to invoke when the `[]` method is unable to
-locate a BookingStatus record for arg.  The default is the built-in `:enforce_none` which returns nil. There are also
+locate a BookingStatus record for arg. The default is the built-in `:enforce_none` which returns nil. There are also
 built-ins for `:enforce_strict` (raise and exception regardless of the type for arg), `:enforce_strict_literals` (raises
 an exception if the arg is a Fixnum or Symbol), `:enforce_strict_ids` (raises and exception if the arg is a Fixnum) and
 `:enforce_strict_symbols` (raises an exception if the arg is a Symbol).
 
 The purpose of the `:on_lookup_failure` option is that a) under some circumstances a lookup failure is a Bad Thing and
-action should be taken, therefore b) a fallback action should be easily configurable.  As of version 0.8.4, you can
+action should be taken, therefore b) a fallback action should be easily configurable. As of version 0.8.4, you can
 also set `:on_lookup_failure` to a lambda that takes in a single argument (The arg that was passed to `[]`).
 
-As of version 0.8.0, you can pass in multiple arguments to `[]`.  This returns a list of enums corresponding to the
-passed in values.  Duplicates are filtered out.  For example `BookingStatus[arg1, arg2, arg3]` would be equivalent to
+As of version 0.8.0, you can pass in multiple arguments to `[]`. This returns a list of enums corresponding to the
+passed in values. Duplicates are filtered out. For example `BookingStatus[arg1, arg2, arg3]` would be equivalent to
 `[BookingStatus[arg1], BookingStatus[arg2], BookingStatus[arg3]]`.
 
 ##### contains?(arg) (since version 0.10.0)
 
 `BookingStatus.contains?(arg)` returns `true if` the given Symbol, String or id has a member instance in the enumeration,
-`false` otherwise.  Returns `true` if the argument is an enum instance, returns `false` if the argument  is `nil` or any
+`false` otherwise. Returns `true` if the argument is an enum instance, returns `false` if the argument  is `nil` or any
 other value.
 
 ##### all
@@ -327,12 +332,12 @@ other value.
 
 ##### active
 
-`BookingStatus.active` returns an array of all BookingStatus records that are marked active.  See the `active?` instance
+`BookingStatus.active` returns an array of all BookingStatus records that are marked active. See the `active?` instance
 method.
 
 ##### inactive
 
-`BookingStatus.inactive` returns an array of all BookingStatus records that are inactive.  See the `inactive?` instance
+`BookingStatus.inactive` returns an array of all BookingStatus records that are inactive. See the `inactive?` instance
 method.
 
 ##### names (since version 0.6.3)
@@ -341,7 +346,7 @@ method.
 
 ##### update\_enumerations\_model (since version 0.8.1)
 
-The preferred mechanism to update an enumerations model in migrations and similar.  Pass in a block to this method to
+The preferred mechanism to update an enumerations model in migrations and similar. Pass in a block to this method to
 to perform any updates.
 
 Example:
@@ -366,7 +371,7 @@ end
 
 ##### acts\_as\_enumerated? (since version 0.8.6)
 
-Returns `true` for ActiveRecord models that act as enumerated, `false` for others.  So
+Returns `true` for ActiveRecord models that act as enumerated, `false` for others. So
 `BookingStatus.acts_as_enumerated?` would return `true`, while `Booking.acts_as_enumerated?` would return `false`.
 
 #### Instance Methods
@@ -415,12 +420,12 @@ Returns the string representation of the enum, i.e. the value in the `:name_colu
 
 ##### name
 
-By default, aliased to the string representation of the `:name_column` attribute.  To avoid this, set the `alias_name`
+By default, aliased to the string representation of the `:name_column` attribute. To avoid this, set the `alias_name`
 option to `false`.
 
 ##### name\_sym
 
-Returns the symbol representation of the name of the enum.  `BookingStatus[:foo].name_sym` returns :foo.
+Returns the symbol representation of the name of the enum. `BookingStatus[:foo].name_sym` returns :foo.
 
 ##### to\_sym
 
@@ -428,20 +433,20 @@ Aliased to `name_sym` (Since version 0.9.0).
 
 ##### active?
 
-Returns true if the instance is active, false otherwise.  If it has an attribute 'active',
-returns the attribute cast to a boolean, otherwise returns true.  This method is used by the `active`
+Returns true if the instance is active, false otherwise. If it has an attribute 'active',
+returns the attribute cast to a boolean, otherwise returns true. This method is used by the `active`
 class method to select active enums.
 
 ##### inactive?
 
-Returns true if the instance is inactive, false otherwise.  Default implementations returns `!active?`
+Returns true if the instance is inactive, false otherwise. Default implementations returns `!active?`
 This method is used by the `inactive` class method to select inactive enums.
 
 #### Notes
 
 `acts_as_enumerated` records are considered immutable. By default you cannot create/alter/destroy instances because they
-are cached in memory.  Because of Rails' process-based model it is not safe to allow updating acts\_as\_enumerated
-records as the caches will get out of sync.  Also, as of version 0.5.1, `to_s` is overriden to return the name of the
+are cached in memory. Because of Rails' process-based model it is not safe to allow updating acts\_as\_enumerated
+records as the caches will get out of sync. Also, as of version 0.5.1, `to_s` is overriden to return the name of the
 enum instance.
 
 However, one instance where updating the models *should* be allowed is if you are using seeds.rb to seed initial values
@@ -461,7 +466,7 @@ Note that a `:presence` and `:uniqueness` validation is automatically defined on
 ### has\_enumerated
 
 First of all, note that you *could* specify the relationship to an `acts_as_enumerated` class using the `belongs_to`
-association.  However, `has_enumerated` is preferable because you aren't really associated to the enumerated value, you
+association. However, `has_enumerated` is preferable because you aren't really associated to the enumerated value, you
 are *aggregating* it. As such, the `has_enumerated` macro behaves more like an aggregation than an association.
 
 ```ruby
@@ -470,19 +475,19 @@ class Booking < ActiveRecord::Base
                   :class_name        => 'BookingStatus',
                   :foreign_key       => 'status_id',
                   :on_lookup_failure => :optional_instance_method,
-                  :permit_empty_name => true,  #Setting this to true disables automatic conversion of empty strings to nil.  Default is false.
+                  :permit_empty_name => true,  #Setting this to true disables automatic conversion of empty strings to nil. Default is false.
                   :default           => :unconfirmed,  #Default value of the attribute.
                   :create_scope      => false  #Setting this to false disables the automatic creation of the 'with_status' scope.
 end
 ```
 
 By default, the foreign key is interpreted to be the name of your has\_enumerated field (in this case 'booking\_status')
-plus '\_id'.  Since we chose to make the column name 'status\_id' for the sake of brevity, we must explicitly designate
-it.  Additionally, the default value for `:class_name` is the camelized version of the name for your has\_enumerated
-field. `:on_lookup_failure` is explained below.  `:permit_empty_name` is an optional flag to disable automatic
-conversion of empty strings to nil.  It is typically desirable to have `booking.update_attributes(:status => '')`
+plus '\_id'. Since we chose to make the column name 'status\_id' for the sake of brevity, we must explicitly designate
+it. Additionally, the default value for `:class_name` is the camelized version of the name for your has\_enumerated
+field. `:on_lookup_failure` is explained below. `:permit_empty_name` is an optional flag to disable automatic
+conversion of empty strings to nil. It is typically desirable to have `booking.update_attributes(:status => '')`
 assign status\_id to a nil rather than raise an Error, as you'll be often calling `update_attributes` with form data, but
-the choice is yours.  Setting a `:default` option will generate an after\_initialize callback to set a default value on
+the choice is yours. Setting a `:default` option will generate an after\_initialize callback to set a default value on
 the attribute unless a non-nil value has already been set.
 
 With that, your Booking class will have the following methods defined:
@@ -493,7 +498,7 @@ Returns the BookingStatus with an id that matches the value in the Booking.statu
 
 #### status=(arg)
 
-Sets the value for Booking.status\_id using the id of the BookingStatus instance passed as an argument.  As a
+Sets the value for Booking.status\_id using the id of the BookingStatus instance passed as an argument. As a
 short-hand, you can also pass it the 'name' of a BookingStatus instance, either as a 'string' or :symbol, or pass in the
 id directly.
 
@@ -516,12 +521,12 @@ mybooking.status = BookingStatus[:confirmed]
 ```
 
 The `:on_lookup_failure` option in has\_enumerated is there because you may want to create an error handler for
-situations where the argument passed to `status=(arg)` is invalid.  By default, an invalid value will cause an
+situations where the argument passed to `status=(arg)` is invalid. By default, an invalid value will cause an
 ArgumentError to be raised.
 
-Of course, this may not be optimal in your situation.  In this case you can do one of three things:
+Of course, this may not be optimal in your situation. In this case you can do one of three things:
 
-1) You can set it to 'validation\_error'.  In this case, the invalid value will be cached and returned on
+1) You can set it to 'validation\_error'. In this case, the invalid value will be cached and returned on
 subsequent lookups, but the model will fail validation.
 
 2) Specify an *instance* method to be called in the case of a lookup failure. The method signature is as follows:
@@ -530,13 +535,13 @@ subsequent lookups, but the model will fail validation.
 your_lookup_handler(operation, name, name_foreign_key, acts_enumerated_class_name, lookup_value)
 ```
 
-The 'operation' arg will be either `:read` or `:write`.  In the case of `:read` you are expected to return something or
+The 'operation' arg will be either `:read` or `:write`. In the case of `:read` you are expected to return something or
 raise an exception, while in the case of a `:write` you don't have to return anything.
 
 Note that there's enough information in the method signature that you can specify one method to handle all lookup
 failures for all has\_enumerated fields if you happen to have more than one defined in your model.
 
-3) (Since version 0.8.5) Give it a lambda function.  In that case, the lambda needs to accept the ActiveRecord model as
+3) (Since version 0.8.5) Give it a lambda function. In that case, the lambda needs to accept the ActiveRecord model as
 its first argument, with the rest of the arguments being identical to the signature of the lookup handler instance
 method.
 
@@ -547,18 +552,18 @@ method.
 ```
 
 NOTE: A `nil` is always considered to be a valid value for `status=(arg)` since it's assumed you're trying to null out
-the foreign key.  The `:on_lookup_failure` will be bypassed.
+the foreign key. The `:on_lookup_failure` will be bypassed.
 
 #### with\_enumerated\_attribute scope
 
 Unless the `:create_scope` option is set to `false`, a scope is automatically created that takes a list of enums as
-arguments.  This allows us to say things like:
+arguments. This allows us to say things like:
 
 ```ruby
 Booking.with_status :confirmed, :received
 ```
 
-Strings, symbols, ids, or enum instances are all valid arguments.  For example, the following would be valid, though not
+Strings, symbols, ids, or enum instances are all valid arguments. For example, the following would be valid, though not
 recommended for obvious reasons.
 
 ```ruby
@@ -570,7 +575,7 @@ As of version 0.5.5, it also aliases a pluralized version of the scope, i.e. `:w
 #### exclude\_enumerated\_attribute scope
 
 As of version 0.8.0, a scope for the inverse of `with_enumerated_attribute` is created, unless the `:create_scope`
-option is set to `false`.  As a result, this allows us to do things like
+option is set to `false`. As a result, this allows us to do things like
 
 ```ruby
 Booking.exclude_status :received
@@ -588,7 +593,7 @@ The following methods are added to ActiveRecord::Base as class methods.
 
 #### has\_enumerated?(attr)
 
-Returns true if the given attr is an enumerated attributes, false otherwise.  `attr` can be a string or a symbol.  This
+Returns true if the given attr is an enumerated attributes, false otherwise. `attr` can be a string or a symbol. This
 is a class method.
 
 #### enumerated\_attributes
@@ -597,7 +602,7 @@ Returns an array of attributes which are enumerated.
 
 ### ActiveRecord::VirtualEnumerations
 
-In many instances, your `acts_as_enumerated` classes will do nothing more than just act as enumerated.  In that case,
+In many instances, your `acts_as_enumerated` classes will do nothing more than just act as enumerated. In that case,
 you can use ActiveRecord::VirtualEnumerations to reduce that clutter.
 
 Create a custom Rails initializer: Rails.root/config/initializers/virtual\_enumerations.rb
@@ -632,9 +637,9 @@ ActiveRecord::VirtualEnumerations.define do |config|
 end
 ```
 
-Only the 'ClassName' argument is required.  `:table_name` is used to define a custom table name while the `:extends`
-option is used to set a custom superclass.  Class names can be either camel-cased like ClassName or with
-underscores, like class\_name.  Strings and symbols are both fine.
+Only the 'ClassName' argument is required. `:table_name` is used to define a custom table name while the `:extends`
+option is used to set a custom superclass. Class names can be either camel-cased like ClassName or with
+underscores, like class\_name. Strings and symbols are both fine.
 
 If you need to fine-tune the definition of the enum class, you can optionally pass in a block, which will be
 evaluated in the context of the enum class.
@@ -679,7 +684,7 @@ A pair of custom RSpec matchers are included to streamline testing of enums and
 
 #### act\_as\_enumerated
 
-This is used to test that a model acts as enumerated.  Example:
+This is used to test that a model acts as enumerated. Example:
 
 ```ruby
 describe BookingStatus do
@@ -707,7 +712,7 @@ describe BookingStatus do
 end
 ```
 
-You can also pass in hashes if you want to be thorough and test out all the attributes of each enum.  If
+You can also pass in hashes if you want to be thorough and test out all the attributes of each enum. If
 you do this, you must pass in the `:name` attribute in each hash
 
 ```ruby
@@ -795,12 +800,12 @@ Go back to gem root directory:
 * Initial Test Suite Copyright (c) 2011 Sergey Potapov
 * Subsequent Updates Copyright (c) 2011-2013 Arthur Shagall
 
-Released under the MIT License.  See the LICENSE file for more details.
+Released under the MIT License. See the LICENSE file for more details.
 
 ## Contributing
 
-Contributions are welcome.  However, please make sure of the following before issuing a pull request:
+Contributions are welcome. However, please make sure of the following before issuing a pull request:
 
 * All specs are passing.
-* Any new features have test coverage.  Use the SimpleCov report to confirm.
+* Any new features have test coverage. Use the SimpleCov report to confirm.
 * Anything that breaks backward compatibility has a very good reason for doing so.

metadata

@@ -1,7 +1,8 @@
 --- !ruby/object:Gem::Specification
 name: power_enum
 version: !ruby/object:Gem::Version
-  version: 1.3.3
+  version: 1.3.4
+  prerelease: 
 platform: ruby
 authors:
 - Trevor Squires
@@ -39,11 +40,12 @@ cert_chain:
   amZaYUtWM2wwYTFkR2wyUVNMa2pScFFaRDFiRCtVSDdnT3F5N1piZGNzUkJM
   NEg3VTV6VQpibEtkZEg2dXhDckRTTTdLYWJrelNPVmYKLS0tLS1FTkQgQ0VS
   VElGSUNBVEUtLS0tLQo=
-date: 2013-06-28 00:00:00.000000000 Z
+date: 2013-08-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
   requirement: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -51,6 +53,7 @@ dependencies:
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -58,6 +61,7 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: jeweler
   requirement: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
@@ -65,6 +69,7 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
@@ -72,6 +77,7 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: yard
   requirement: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
@@ -79,6 +85,7 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
@@ -86,6 +93,7 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
@@ -93,6 +101,7 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
@@ -100,6 +109,7 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: sqlite3
   requirement: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
@@ -107,6 +117,7 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
@@ -114,6 +125,7 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: genspec
   requirement: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
@@ -121,6 +133,7 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
+    none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
@@ -163,27 +176,29 @@ files:
 - LICENSE
 - README.markdown
 homepage: http://github.com/albertosaurus/power_enum
-licenses: []
-metadata: {}
+licenses:
+- MIT
 post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
+  none: false
   requirements:
   - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
+  none: false
   requirements:
   - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.0.3
+rubygems_version: 1.8.25
 signing_key: 
-specification_version: 4
+specification_version: 3
 summary: Allows you to treat instances of your ActiveRecord models as though they
   were an enumeration of values
 test_files: []

checksums.yaml

@@ -1,15 +0,0 @@
----
-!binary "U0hBMQ==":
-  metadata.gz: !binary |-
-    YTUwNmE0YTk3MTlmNTg1ZWU0ZTYwZjQ4NWZkODRlMDM2YTNmNWNhZg==
-  data.tar.gz: !binary |-
-    ODQzZjYyZGI3ZTFkNmMzZjM4ZTEwZjAzOWFhNjdlNDE2ZTgwNjA2OA==
-!binary "U0hBNTEy":
-  metadata.gz: !binary |-
-    YjBmNDRhYTIwZjM3ZTY2OGRkOGE5YzA0NTEwZmQwZDZhYmZjNGUxZjRjZDA5
-    OGI1YzgyZmRjZjY3NDJhMmNhMzVkZTlmMjBlMDFlMmI2ZjdiY2ZhZTdjM2M4
-    MjU3NTJmOTgyZTBjZjQxYTFiNTY3YWU1MGZiYTYyMDBhNGQ1ZmU=
-  data.tar.gz: !binary |-
-    MTc3NWQ1ZWNlNzY5YTE2ZjA1Y2Y4NTBhMzNiMTY3YjkyMTA1ZmFhYjFmZDJk
-    NjM4NzVmNzQ4ZGVhYjJkMjZlNTRhNDAxYjU0NGM1OGVjZDg1NGMxM2RlOWNl
-    NjNjYTk4ZWZjZDMyZDEwM2JkMWUxMGJjMTQ5YzhjMWE1OWYzMWM=