amoeba 1.2.0 → 1.2.1

data/.rvmrc

@@ -1 +1 @@
-rvm use --create 1.9.3-p0@amoeba
+rvm use --create 1.9.3-p125@amoeba

data/README.md

@@ -4,29 +4,19 @@ Easy copying of rails associations such as `has_many`.
 
 ![amoebalogo](http://rocksolidwebdesign.com/wp_cms/wp-content/uploads/2012/02/amoeba_logo.jpg)
 
-## Installation
-
-is hopefully as you would expect:
-
-    gem install amoeba
-
-or just add it to your Gemfile:
-
-    gem 'amoeba'
-
 ## What?
 
 The goal was to be able to easily and quickly reproduce ActiveRecord objects including their children, for example copying a blog post maintaining its associated tags or categories.
 
 This gem is named "Amoeba" because amoebas are (small life forms that are) good at reproducing. Their children and grandchildren also reproduce themselves quickly and easily.
 
-## Details
+### Technical Details
 
 An ActiveRecord extension gem to allow the duplication of associated child record objects when duplicating an active record model. This gem overrides and adds to the built in `ActiveRecord::Base#dup` method.
 
 Rails 3.2 compatible.
 
-## Features
+### Features
 
 - Supports the following association types
     - `has_many`
@@ -50,6 +40,16 @@ Rails 3.2 compatible.
 
 ## Usage
 
+### Installation
+
+is hopefully as you would expect:
+
+    gem install amoeba
+
+or just add it to your Gemfile:
+
+    gem 'amoeba'
+
 Configure your models with one of the styles below and then just run the `dup` method on your model as you normally would:
 
     p = Post.create(:title => "Hello World!", :content => "Lorum ipsum dolor")
@@ -67,11 +67,11 @@ By default, when enabled, amoeba will copy any and all associated child records
 
 You can configure the behavior to only include fields that you list or to only include fields that you don't exclude. Of the three, the most performant will be the indiscriminate style, followed by the inclusive style, and the exclusive style will be the slowest because of the need for an extra explicit check on each field. This performance difference is likely negligible enough that you can choose the style to use based on which is easiest to read and write, however, if your data tree is large enough and you need control over what fields get copied, inclusive style is probably a better choice than exclusive style.
 
-## Configuration
+### Configuration
 
 Please note that these examples are only loose approximations of real world scenarios and may not be particularly realistic, they are only for the purpose of demonstrating feature usage.
 
-### Indiscriminate Style
+#### Indiscriminate Style
 
 This is the most basic usage case and will simply enable the copying of any known associations.
 
@@ -101,7 +101,7 @@ simply add the amoeba configuration block to your model and call the enable meth
 
 Child records will be automatically copied when you run the dup method.
 
-### Inclusive Style
+#### Inclusive Style
 
 If you only want some of the associations copied but not others, you may use the inclusive style:
 
@@ -158,7 +158,7 @@ These examples will copy the post's tags and authors but not its comments.
 
 The inclusive style, when used, will automatically disable any ther style that was previously selected.
 
-### Exclusive Style
+#### Exclusive Style
 
 If you have more fields to include than to exclude, you may wish to shorten the amount of typing and reading you need to do by using the exclusive style. All fields that are not explicitly excluded will be copied:
 
@@ -180,7 +180,7 @@ This example does the same thing as the inclusive style example, it will copy th
 
 The exclusive style, when used, will automatically disable any other style that was previously selected, so if you selected include fields, and then you choose some exclude fields, the `exclude_field` method will disable the previously slected inclusive style and wipe out any corresponding include fields.
 
-### Cloning
+#### Cloning
 
 If you are using a Many-to-Many relationship, you may tell amoeba to actually make duplicates of the original related records rather than merely maintaining association with the original records. Cloning is easy, merely tell amoeba which fields to clone in the same way you tell it which fields to include or exclude.
 
@@ -212,217 +212,119 @@ If you are using a Many-to-Many relationship, you may tell amoeba to actually ma
 
 This example will actually duplicate the warnings and widgets in the database. If there were originally 3 warnings in the database then, upon duplicating a post, you will end up with 6 warnings in the database. This is in contrast to the default behavior where your new post would merely be re-associated with any previously existing warnings and those warnings themselves would not be duplicated.
 
-## Inheritance
-
-If you are using the Single Table Inheritance provided by ActiveRecord, you may cause amoeba to automatically process child classes in the same way as their parents. All you need to do is call the `propagate` method within the amoeba block of the parent class and all child classes should copy in a similar manner.
-
-    create_table :products, :force => true do |t|
-      t.string :type # this is the STI column
+### Limiting Association Types
 
-      # these belong to all products
-      t.string :title
-      t.decimal :price
+By default, amoeba recognizes and attemps to copy any children of the following association types:
 
-      # these are for shirts only
-      t.decimal :sleeve_length
-      t.decimal :collar_size
+ - has one
+ - has many
+ - has and belongs to many
 
-      # these are for computers only
-      t.integer :ram_size
-      t.integer :hard_drive_size
-    end
+You may control which association types amoeba applies itself to by using the `recognize` method within the amoeba configuration block.
 
-    class Product < ActiveRecord::Base
-      has_many :images
-      has_and_belongs_to_many :categories
+    class Post < ActiveRecord::Base
+      has_one :config
+      has_many :comments
+      has_and_belongs_to_many :tags
 
       amoeba do
-        enable
-        propagate
+        recognize [:has_one, :has_and_belongs_to_many]
       end
     end
 
-    class Shirt < Product
-    end
-
-    class Computer < Product
+    class Comment < ActiveRecord::Base
+      belongs_to :post
     end
 
-    class ProductsController
-      def some_method
-        my_shirt = Shirt.find(1)
-        my_shirt.dup
-        my_shirt.save
-
-        # this shirt should now:
-        # - have its own copy of all parent images
-        # - be in the same categories as the parent
-      end
+    class Tag < ActiveRecord::Base
+      has_and_belongs_to_many :posts
     end
 
-This example should duplicate all the images and sections associated with this Shirt, which is a child of Product
-
-### Parenting Style
-
-By default, propagation uses submissive parenting, meaning the config settings on the parent will be applied, but any child settings, if present, will either add to or overwrite the parent settings depending on how you call the DSL methods.
+This example will copy the post's configuration data and keep tags associated with the new post, but will not copy the post's comments because amoeba will only recognize and copy children of `has_one` and `has_and_belongs_to_many` associations and in this example, comments are not an `has_and_belongs_to_many` association.
 
-You may change this behavior, the so called "parenting style", to give preference to the parent settings or to ignore any and all child settings.
+### Nested Association Validation
 
-#### Relaxed Parenting
+If you end up with some validation issues when trying to validate the presence of a child's `belongs_to` association, just be sure to include the `:inverse_of` declaration on your relationships and all should be well.
 
-The `:relaxed` parenting style will prefer parent settings.
+For example this will throw a validation error saying that your posts are invalid:
 
-    class Product < ActiveRecord::Base
-      has_many :images
-      has_and_belongs_to_many :sections
+    class Author < ActiveRecord::Base
+      has_many :posts
 
       amoeba do
-        exclude_field :images
-        propagate :relaxed
+        enable
       end
     end
 
-    class Shirt < Product
-      include_field :images
-      include_field :sections
-      prepend :title => "Copy of "
-    end
-
-In this example, the conflicting `include_field` settings on the child will be ignored and the parent `exclude_field` setting will be used, while the `prepend` setting on the child will be honored because it doesn't conflict with the parent.
-
-#### Strict Parenting
-
-The `:strict` style will ignore child settings altogether and inherit any parent settings.
-
-    class Product < ActiveRecord::Base
-      has_many :images
-      has_and_belongs_to_many :sections
+    class Post < ActiveRecord::Base
+      belongs_to :author
+      validates_presence_of :author
 
       amoeba do
-        exclude_field :images
-        propagate :strict
+        enable
       end
     end
 
-    class Shirt < Product
-      include_field :images
-      include_field :sections
-      prepend :title => "Copy of "
-    end
-
-In this example, the only processing that will happen when a Shirt is duplicated is whatever processing is allowed by the parent. So in this case the parent's `exclude_field` directive takes precedence over the child's `include_field` settings, and not only that, but none of the other settings for the child are used either. The `prepend` setting of the child is completely ignored.
-
-#### Parenting and Precedence
-
-Because of the two general forms of DSL config parameter usage, you may wish to make yourself mindful of how your coding style will affect the outcome of duplicating an object.
-
-Just remember that:
-
-* If you pass an array you will wipe all previous settings
-* If you pass single values, you will add to currently existing settings
-
-This means that, for example:
-
-* When using the submissive parenting style, you can child take full precedence on a per field basis by passing an array of config values. This will cause the setting from the parent to be overridden instead of added to.
-* When using the relaxed parenting style, you can still let the parent take precedence on a per field basis by passing an array of config values. This will cause the setting for that child to be overridden instead of added to.
+    author = Author.find(1)
+    author.dup
 
-#### A Submissive Override Example
+    author.save # this will fail validation
 
-This version will use both the parent and child settings, so both the images and sections will be copied.
+Wheras this will work fine:
 
-    class Product < ActiveRecord::Base
-      has_many :images
-      has_and_belongs_to_many :sections
+    class Author < ActiveRecord::Base
+      has_many :posts, :inverse_of => :author
 
       amoeba do
-        include_field :images
-        propagate
+        enable
       end
     end
 
-    class Shirt < Product
-      include_field :sections
-    end
-
-The next version will use only the child settings because passing an array will override any previous settings rather than adding to them and the child config takes precedence in the `submissive` parenting style. So in this case only the sections will be copied.
-
-    class Product < ActiveRecord::Base
-      has_many :images
-      has_and_belongs_to_many :sections
+    class Post < ActiveRecord::Base
+      belongs_to :author, :inverse_of => :posts
+      validates_presence_of :author
 
       amoeba do
-        include_field :images
-        propagate
+        enable
       end
     end
 
-    class Shirt < Product
-      include_field [:sections]
-    end
+    author = Author.find(1)
+    author.dup
 
-#### A Relaxed Override Example
+    author.save # this will pass validation
 
-This version will use both the parent and child settings, so both the images and sections will be copied.
-
-    class Product < ActiveRecord::Base
-      has_many :images
-      has_and_belongs_to_many :sections
+This issue is not amoeba specific and also occurs when creating new objects using `accepts_nested_attributes_for`, like this:
 
-      amoeba do
-        include_field :images
-        propagate :relaxed
-      end
+    class Author < ActiveRecord::Base
+      has_many :posts
+      accepts_nested_attributes_for :posts
     end
 
-    class Shirt < Product
-      include_field :sections
+    class Post < ActiveRecord::Base
+      belongs_to :author
+      validates_presence_of :author
     end
 
-The next version will use only the parent settings because passing an array will override any previous settings rather than adding to them and the parent config takes precedence in the `relaxed` parenting style. So in this case only the images will be copied.
-
-    class Product < ActiveRecord::Base
-      has_many :images
-      has_and_belongs_to_many :sections
+    # this will fail validation
+    author = Author.create({:name => "Jim Smith", :posts => [{:title => "Hello World", :contents => "Lorum ipsum dolor}]})
 
-      amoeba do
-        include_field [:images]
-        propagate
-      end
-    end
+This issue with `accepts_nested_attributes_for` can also be solved by using `:inverse_of`, like this:
 
-    class Shirt < Product
-      include_field :sections
+    class Author < ActiveRecord::Base
+      has_many :posts, :inverse_of => :author
+      accepts_nested_attributes_for :posts
     end
 
-### Limiting Association Types
-
-By default, amoeba recognizes and attemps to copy any children of the following association types:
-
- - has one
- - has many
- - has and belongs to many
-
-You may control which association types amoeba applies itself to by using the `recognize` method within the amoeba configuration block.
-
     class Post < ActiveRecord::Base
-      has_one :config
-      has_many :comments
-      has_and_belongs_to_many :tags
-
-      amoeba do
-        recognize [:has_one, :has_and_belongs_to_many]
-      end
-    end
-
-    class Comment < ActiveRecord::Base
-      belongs_to :post
+      belongs_to :author, :inverse_of => :posts
+      validates_presence_of :author
     end
 
-    class Tag < ActiveRecord::Base
-      has_and_belongs_to_many :posts
-    end
+    # this will pass validation
+    author = Author.create({:name => "Jim Smith", :posts => [{:title => "Hello World", :contents => "Lorum ipsum dolor}]})
 
-This example will copy the post's configuration data and keep tags associated with the new post, but will not copy the post's comments because amoeba will only recognize and copy children of `has_one` and `has_and_belongs_to_many` associations and in this example, comments are not an `has_and_belongs_to_many` association.
+The crux of the issue is that upon duplication, the new `Author` instance does not yet have an ID because it has not yet been persisted, so the `:posts` do not yet have an `:author_id` either, and thus no `:author` and thus they will fail validation. This issue may likely affect amoeba usage so if you get some validation failures, be sure to add `:inverse_of` to your models.
 
 ### Field Preprocessors
 
@@ -500,6 +402,8 @@ You may run a search and replace query on a copied object's field during the cop
 
 #### Custom Methods
 
+##### Customize
+
 You may run a custom method or methods to do basically anything you like, simply pass a lambda block, or an array of lambda blocks to the `customize` directive. Each block must have the same form, meaning that each block must accept two parameters, the original object and the newly copied object. You may then do whatever you wish, like this:
 
     class Post < ActiveRecord::Base
@@ -536,9 +440,27 @@ or this, using an array:
       end
     end
 
+##### Override
+
+Lambda blocks passed to customize run, by default, after all copying and field pre-processing. If you wish to run a method before any customization or field pre-processing, you may use `override` the cousin of `customize`. Usage is the same as above.
+
+    class Post < ActiveRecord::Base
+      amoeba do
+        prepend :title => "Hello world! "
+
+        override(lambda { |original_post,new_post|
+          if original_post.foo == "bar"
+            new_post.baz = "qux"
+          end
+        })
+
+        append :comments => "... know what I'm sayin?"
+      end
+    end
+
 #### Chaining
 
-You may apply a preprocessor to multiple fields at once.
+You may apply a single preprocessor to multiple fields at once.
 
     class Post < ActiveRecord::Base
       amoeba do
@@ -739,29 +661,211 @@ You may control how amoeba copies your object, on the fly, by passing a configur
       end
     end
 
-### Configuration Reference
+### Inheritance
+
+If you are using the Single Table Inheritance provided by ActiveRecord, you may cause amoeba to automatically process child classes in the same way as their parents. All you need to do is call the `propagate` method within the amoeba block of the parent class and all child classes should copy in a similar manner.
+
+    create_table :products, :force => true do |t|
+      t.string :type # this is the STI column
+
+      # these belong to all products
+      t.string :title
+      t.decimal :price
+
+      # these are for shirts only
+      t.decimal :sleeve_length
+      t.decimal :collar_size
+
+      # these are for computers only
+      t.integer :ram_size
+      t.integer :hard_drive_size
+    end
+
+    class Product < ActiveRecord::Base
+      has_many :images
+      has_and_belongs_to_many :categories
+
+      amoeba do
+        enable
+        propagate
+      end
+    end
+
+    class Shirt < Product
+    end
+
+    class Computer < Product
+    end
+
+    class ProductsController
+      def some_method
+        my_shirt = Shirt.find(1)
+        my_shirt.dup
+        my_shirt.save
+
+        # this shirt should now:
+        # - have its own copy of all parent images
+        # - be in the same categories as the parent
+      end
+    end
+
+This example should duplicate all the images and sections associated with this Shirt, which is a child of Product
+
+#### Parenting Style
+
+By default, propagation uses submissive parenting, meaning the config settings on the parent will be applied, but any child settings, if present, will either add to or overwrite the parent settings depending on how you call the DSL methods.
+
+You may change this behavior, the so called "parenting style", to give preference to the parent settings or to ignore any and all child settings.
+
+##### Relaxed Parenting
+
+The `:relaxed` parenting style will prefer parent settings.
+
+    class Product < ActiveRecord::Base
+      has_many :images
+      has_and_belongs_to_many :sections
+
+      amoeba do
+        exclude_field :images
+        propagate :relaxed
+      end
+    end
+
+    class Shirt < Product
+      include_field :images
+      include_field :sections
+      prepend :title => "Copy of "
+    end
+
+In this example, the conflicting `include_field` settings on the child will be ignored and the parent `exclude_field` setting will be used, while the `prepend` setting on the child will be honored because it doesn't conflict with the parent.
+
+##### Strict Parenting
+
+The `:strict` style will ignore child settings altogether and inherit any parent settings.
+
+    class Product < ActiveRecord::Base
+      has_many :images
+      has_and_belongs_to_many :sections
+
+      amoeba do
+        exclude_field :images
+        propagate :strict
+      end
+    end
+
+    class Shirt < Product
+      include_field :images
+      include_field :sections
+      prepend :title => "Copy of "
+    end
+
+In this example, the only processing that will happen when a Shirt is duplicated is whatever processing is allowed by the parent. So in this case the parent's `exclude_field` directive takes precedence over the child's `include_field` settings, and not only that, but none of the other settings for the child are used either. The `prepend` setting of the child is completely ignored.
+
+##### Parenting and Precedence
+
+Because of the two general forms of DSL config parameter usage, you may wish to make yourself mindful of how your coding style will affect the outcome of duplicating an object.
+
+Just remember that:
+
+* If you pass an array you will wipe all previous settings
+* If you pass single values, you will add to currently existing settings
+
+This means that, for example:
+
+* When using the submissive parenting style, you can child take full precedence on a per field basis by passing an array of config values. This will cause the setting from the parent to be overridden instead of added to.
+* When using the relaxed parenting style, you can still let the parent take precedence on a per field basis by passing an array of config values. This will cause the setting for that child to be overridden instead of added to.
+
+##### A Submissive Override Example
+
+This version will use both the parent and child settings, so both the images and sections will be copied.
+
+    class Product < ActiveRecord::Base
+      has_many :images
+      has_and_belongs_to_many :sections
+
+      amoeba do
+        include_field :images
+        propagate
+      end
+    end
+
+    class Shirt < Product
+      include_field :sections
+    end
+
+The next version will use only the child settings because passing an array will override any previous settings rather than adding to them and the child config takes precedence in the `submissive` parenting style. So in this case only the sections will be copied.
+
+    class Product < ActiveRecord::Base
+      has_many :images
+      has_and_belongs_to_many :sections
+
+      amoeba do
+        include_field :images
+        propagate
+      end
+    end
+
+    class Shirt < Product
+      include_field [:sections]
+    end
+
+##### A Relaxed Override Example
+
+This version will use both the parent and child settings, so both the images and sections will be copied.
+
+    class Product < ActiveRecord::Base
+      has_many :images
+      has_and_belongs_to_many :sections
+
+      amoeba do
+        include_field :images
+        propagate :relaxed
+      end
+    end
+
+    class Shirt < Product
+      include_field :sections
+    end
+
+The next version will use only the parent settings because passing an array will override any previous settings rather than adding to them and the parent config takes precedence in the `relaxed` parenting style. So in this case only the images will be copied.
+
+    class Product < ActiveRecord::Base
+      has_many :images
+      has_and_belongs_to_many :sections
+
+      amoeba do
+        include_field [:images]
+        propagate
+      end
+    end
+
+    class Shirt < Product
+      include_field :sections
+    end
+
+## Configuration Reference
 
 Here is a static reference to the available configuration methods, usable within the amoeba block on your rails models.
 
-#### Controlling Associations
+### Controlling Associations
 
-* `enable`
+#### enable
 
   Enables amoeba in the default style of copying all known associated child records. Using the enable method is only required if you wish to enable amoeba but you are not using either the `include_field` or `exclude_field` directives. If you use either inclusive or exclusive style, amoeba is automatically enabled for you, so calling `enable` would be redundant, though it won't hurt.
 
-* `include_field`
+#### include_field
 
   Adds a field to the list of fields which should be copied. All associations not in this list will not be copied. This method may be called multiple times, once per desired field, or you may pass an array of field names. Passing a single symbol will add to the list of included fields. Passing an array will empty the list and replace it with the array you pass.
 
-* `exclude_field`
+#### exclude_field
 
   Adds a field to the list of fields which should not be copied. Only the associations that are not in this list will be copied. This method may be called multiple times, once per desired field, or you may pass an array of field names. Passing a single symbol will add to the list of excluded fields. Passing an array will empty the list and replace it with the array you pass.
 
-* `clone`
+#### clone
 
   Adds a field to the list of associations which should have their associated children actually cloned. This means for example, that instead of just maintaining original associations with previously existing tags, a copy will be made of each tag, and the new record will be associated with these new tag copies rather than the old tag copies. This method may be called multiple times, once per desired field, or you may pass an array of field names. Passing a single symbol will add to the list of excluded fields. Passing an array will empty the list and replace it with the array you pass.
 
-* `propagate`
+#### propagate
 
   This causes any inherited child models to take the same config settings when copied. This method may take up to one argument to control the so called "parenting style". The argument should be one of `strict`, `relaxed` or `submissive`.
 
@@ -775,7 +879,7 @@ Here is a static reference to the available configuration methods, usable within
 
   will choose the strict parenting style of inherited settings.
 
-* `raised`
+#### raised
 
   This causes any child to behave with a (potentially) different "parenting style" than its actual parent. This method takes up to a single parameter for which there are three options, `strict`, `relaxed` and `submissive`.
 
@@ -789,29 +893,29 @@ Here is a static reference to the available configuration methods, usable within
 
   will choose the relaxed parenting style of inherited settings for this child. A parenting style set via the `raised` method takes precedence over the parenting style set using the `propagate` method.
 
-#### Pre-Processing Fields
+### Pre-Processing Fields
 
-* `nullify`
+#### nullify
 
   Adds a field to the list of non-association based fields which should be set to nil during copy. All fields in this list will be set to `nil` - note that any nullified field will be given its default value if a default value exists on this model's migration. This method may be called multiple times, once per desired field, or you may pass an array of field names. Passing a single symbol will add to the list of null fields. Passing an array will empty the list and replace it with the array you pass.
 
-* `prepend`
+#### prepend
 
   Prefix a field with some text. This only works for string fields. Accepts a hash of fields to prepend. The keys are the field names and the values are the prefix strings. An example scenario would be to add a string such as "Copy of " to your title field. Don't forget to include extra space to the right if you want it. Passing a hash will add each key value pair to the list of prepend directives. If you wish to empty the list of directives, you may pass the hash inside of an array like this `[{:title => "Copy of "}]`.
 
-* `append`
+#### append
 
   Append some text to a field. This only works for string fields. Accepts a hash of fields to prepend. The keys are the field names and the values are the prefix strings. An example would be to add " (copied version)" to your description field. Don't forget to add a leading space if you want it. Passing a hash will add each key value pair to the list of append directives. If you wish to empty the list of directives, you may pass the hash inside of an array like this `[{:contents => " (copied version)"}]`.
 
-* `set`
+#### set
 
   Set a field to a given value. This sould work for almost any type of field. Accepts a hash of fields and the values you want them set to.. The keys are the field names and the values are the prefix strings. An example would be to add " (copied version)" to your description field. Don't forget to add a leading space if you want it. Passing a hash will add each key value pair to the list of append directives. If you wish to empty the list of directives, you may pass the hash inside of an array like this `[{:approval_state => "open_for_editing"}]`.
 
-* `regex`
+#### regex
 
   Globally search and replace the field for a given pattern. Accepts a hash of fields to run search and replace upon. The keys are the field names and the values are each a hash with information about what to find and what to replace it with. in the form of . An example would be to replace all occurrences of the word "dog" with the word "cat", the parameter hash would look like this `:contents => {:replace => /dog/, :with => "cat"}`. Passing a hash will add each key value pair to the list of regex directives. If you wish to empty the list of directives, you may pass the hash inside of an array like this `[{:contents => {:replace => /dog/, :with => "cat"}]`.
 
-* `customize`
+#### customize
 
   Runs a custom method so you can do basically whatever you want. All you need to do is pass a lambda block or an array of lambda blocks that take two parameters, the original object and the new object copy
 
@@ -825,12 +929,17 @@ The behavior when copying nested hierarchical models is undefined. Copying a cat
 
 The behavior when copying polymorphic `has_many` associations is also undefined. Support for these types of associations is planned for a future release.
 
-### For Developers
+## For Developers
 
 You may run the rspec tests like this:
 
     bundle exec rspec spec
 
+### TODO
+
+* add ability to cancel further processing from within an override block
+* write some spec for the override method
+
 ## License
 
 [The BSD License](http://www.opensource.org/licenses/bsd-license.php)

data/amoeba.gemspec

@@ -28,7 +28,7 @@ EOF
   s.add_development_dependency "bundler", ">= 1.0.0"
   s.add_development_dependency "rspec", "~> 2.3"
 
-  s.add_development_dependency "sqlite3-ruby"
+  s.add_development_dependency "sqlite3"
 
   s.add_dependency "activerecord", ">= 3.0"
 end

data/lib/amoeba.rb

@@ -59,6 +59,11 @@ module Amoeba
         @customizations
       end
 
+      def overrides
+        @overrides ||= []
+        @overrides
+      end
+
       def null_fields
         @null_fields ||= []
         @null_fields
@@ -138,6 +143,17 @@ module Amoeba
         @clones
       end
 
+      def override(value=nil)
+        @do_preproc ||= true
+        @overrides ||= []
+        if value.is_a?(Array)
+          @overrides = value
+        else
+          @overrides << value if value
+        end
+        @overrides
+      end
+
       def customize(value=nil)
         @do_preproc ||= true
         @customizations ||= []
@@ -310,6 +326,7 @@ module Amoeba
     def dup(options={})
       @result = super()
 
+      # Inherit Parent Settings {{{
       if !amoeba_conf.enabled && parent_amoeba_conf.inherit
         if amoeba_conf.upbringing
           parenting_style = amoeba_conf.upbringing
@@ -332,8 +349,16 @@ module Amoeba
           self.class.amoeba(&child_settings)
         end
       end
+      # }}}
 
       # Run Amoeba {{{
+      # pramoeba_conf.overridesepend any extra strings to indicate uniqueness of the new record(s)
+      if amoeba_conf.overrides.length > 0
+        amoeba_conf.overrides.each do |block|
+          block.call(self, @result)
+        end
+      end
+
       if amoeba_conf.enabled
         # Deep Clone Settings {{{
         amoeba_conf.clones.each do |clone_field|
@@ -464,11 +489,6 @@ module Amoeba
         @result[n] = nil
       end
 
-      # prepend any extra strings to indicate uniqueness of the new record(s)
-      amoeba_conf.customizations.each do |block|
-        block.call(self, @result)
-      end
-
       # prepend any extra strings to indicate uniqueness of the new record(s)
       amoeba_conf.coercions.each do |field,coercion|
         @result[field] = "#{coercion}"
@@ -488,6 +508,11 @@ module Amoeba
       amoeba_conf.regexes.each do |field,action|
         @result[field].gsub!(action[:replace], action[:with])
       end
+
+      # prepend any extra strings to indicate uniqueness of the new record(s)
+      amoeba_conf.customizations.each do |block|
+        block.call(self, @result)
+      end
     end
     # }}}
   end

data/lib/amoeba/version.rb

@@ -1,3 +1,3 @@
 module Amoeba
-  VERSION = "1.2.0"
+  VERSION = "1.2.1"
 end

data/spec/lib/amoeba_spec.rb

@@ -33,6 +33,7 @@ describe "amoeba" do
       start_postnote_count = rs["note_count"]
 
       new_post.save
+      new_post.errors.messages.length.should == 0
 
       end_account_count = Account.all.count
       end_history_count = History.all.count
@@ -83,6 +84,12 @@ describe "amoeba" do
         old_post.widgets.map(&:id).include?(id).should_not be true
       end
       # }}}
+      # Author {{{
+      old_author = Author.find(1)
+      new_author = old_author.dup
+      new_author.save
+      new_author.errors.messages.length.should == 0
+      # }}}
       # Products {{{
       # Base Class {{{
       old_product = Product.find(1)
@@ -94,6 +101,7 @@ describe "amoeba" do
 
       new_product = old_product.dup
       new_product.save
+      new_product.errors.messages.length.should == 0
 
       end_image_count = Image.where(:product_id => old_product.id).count
       end_newimage_count = Image.where(:product_id => new_product.id).count
@@ -121,6 +129,7 @@ describe "amoeba" do
 
       new_product = old_product.dup
       new_product.save
+      new_product.errors.messages.length.should == 0
 
       end_image_count = Image.where(:product_id => old_product.id).count
       end_newimage_count = Image.where(:product_id => new_product.id).count
@@ -147,6 +156,7 @@ describe "amoeba" do
 
       new_product = old_product.dup
       new_product.save
+      new_product.errors.messages.length.should == 0
 
       end_image_count = Image.where(:product_id => old_product.id).count
       end_newimage_count = Image.where(:product_id => new_product.id).count

data/spec/support/data.rb

@@ -1,10 +1,13 @@
 u1 = User.create(:name => "Robert Johnson", :email => "bob@crossroads.com")
 u2 = User.create(:name => "Miles Davis", :email => "miles@kindofblue.com")
 
+a1 = Author.create(:full_name => "Kermit The Vonnegut", :nickname => "kvsoitgoes")
+a2 = Author.create(:full_name => "Arthur Sees Clarck", :nickname => "strangewater")
+
 t = Topic.create(:title => "Ponies", :description => "Lets talk about my ponies.")
 
 # First Post {{{
-p1 = t.posts.create(:author => u1, :title => "My little pony", :contents => "Lorum ipsum dolor rainbow bright. I like dogs, dogs are awesome.")
+p1 = t.posts.create(:owner => u1, :author => a1, :title => "My little pony", :contents => "Lorum ipsum dolor rainbow bright. I like dogs, dogs are awesome.")
 f1 = p1.create_post_config(:is_visible => true, :is_open => false, :password => 'abcdefg123')
 a1 = p1.create_account(:title => "Foo")
 h1 = p1.account.create_history(:some_stuff => "Bar")

data/spec/support/models.rb

@@ -2,9 +2,21 @@ class Topic < ActiveRecord::Base
   has_many :posts
 end
 
+class User < ActiveRecord::Base
+  has_many :posts
+end
+
+class Author < ActiveRecord::Base
+  has_many :posts, :inverse_of => :author
+  amoeba do
+    enable
+  end
+end
+
 class Post < ActiveRecord::Base
   belongs_to :topic
-  belongs_to :author, :class_name => 'User'
+  belongs_to :owner, :class_name => 'User'
+  belongs_to :author, :inverse_of => :posts
   has_one :post_config
   has_one :account
   has_one :history, :through => :account
@@ -15,7 +27,9 @@ class Post < ActiveRecord::Base
   has_many :widgets, :through => :post_widgets
   has_and_belongs_to_many :tags
   has_and_belongs_to_many :notes
-  #has_and_belongs_to_many :tags
+
+  validates_presence_of :topic
+  validates_presence_of :author
 
   amoeba do
     enable
@@ -141,10 +155,6 @@ class Note < ActiveRecord::Base
   has_and_belongs_to_many :posts
 end
 
-class User < ActiveRecord::Base
-  has_many :posts
-end
-
 # Inheritance
 class Product < ActiveRecord::Base
   has_many :images

data/spec/support/schema.rb

@@ -9,6 +9,7 @@ ActiveRecord::Schema.define do
 
   create_table :posts, :force => true do |t|
     t.integer :topic_id
+    t.integer :owner_id
     t.integer :author_id
     t.string :title
     t.string :contents
@@ -110,6 +111,12 @@ ActiveRecord::Schema.define do
     t.timestamps
   end
 
+  create_table :authors, :force => true do |t|
+    t.string :full_name
+    t.string :nickname
+    t.timestamps
+  end
+
   create_table :posts_tags, :force => true do |t|
     t.integer :post_id
     t.integer :tag_id

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: amoeba
 version: !ruby/object:Gem::Version
-  version: 1.2.0
+  version: 1.2.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,11 +9,11 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-03-25 00:00:00.000000000 Z
+date: 2012-04-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
-  requirement: &11153980 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
@@ -21,10 +21,15 @@ dependencies:
         version: 1.0.0
   type: :development
   prerelease: false
-  version_requirements: *11153980
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: 1.0.0
 - !ruby/object:Gem::Dependency
   name: rspec
-  requirement: &11153480 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -32,10 +37,15 @@ dependencies:
         version: '2.3'
   type: :development
   prerelease: false
-  version_requirements: *11153480
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '2.3'
 - !ruby/object:Gem::Dependency
-  name: sqlite3-ruby
-  requirement: &11153080 !ruby/object:Gem::Requirement
+  name: sqlite3
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
@@ -43,10 +53,15 @@ dependencies:
         version: '0'
   type: :development
   prerelease: false
-  version_requirements: *11153080
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: activerecord
-  requirement: &11152540 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
@@ -54,7 +69,12 @@ dependencies:
         version: '3.0'
   type: :runtime
   prerelease: false
-  version_requirements: *11152540
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '3.0'
 description: ! 'An extension to ActiveRecord to allow the duplication method to also
   copy associated children, with recursive support for nested of grandchildren. The
   behavior is controllable with a simple DSL both on your rails models and on the
@@ -123,7 +143,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: amoeba
-rubygems_version: 1.8.10
+rubygems_version: 1.8.21
 signing_key: 
 specification_version: 3
 summary: Easy copying of rails models and their child associations.