RubyLearning / ProjectTrak / vendor / rails / railties / doc / guides / source / creating_plugins / migration_generator.txt

== Create a generator ==

Many plugins ship with generators.  When you created the plugin above, you specified the --with-generator option, so you already have the generator stubs in 'vendor/plugins/yaffle/generators/yaffle'.

Building generators is a complex topic unto itself and this section will cover one small aspect of generators:  creating a generator that adds a time-stamped migration.

To create a generator you must:

 * Add your instructions to the 'manifest' method of the generator
 * Add any necessary template files to the templates directory
 * Test the generator manually by running various combinations of `script/generate` and `script/destroy`
 * Update the USAGE file to add helpful documentation for your generator

=== Testing generators ===

Many rails plugin authors do not test their generators, however testing generators is quite simple.  A typical generator test does the following:

 * Creates a new fake rails root directory that will serve as destination
 * Runs the generator forward and backward, making whatever assertions are necessary
 * Removes the fake rails root

For the generator in this section, the test could look something like this:


[source, ruby]
require File.dirname(__FILE__) + '/test_helper.rb'
require 'rails_generator'
require 'rails_generator/scripts/generate'
require 'rails_generator/scripts/destroy'

class GeneratorTest < Test::Unit::TestCase

  def fake_rails_root
    File.join(File.dirname(__FILE__), 'rails_root')
  def file_list
    Dir.glob(File.join(fake_rails_root, "db", "migrate", "*"))

  def setup
    @original_files = file_list

  def teardown
  def test_generates_correct_file_name["yaffle", "bird"], :destination => fake_rails_root)
    new_file = (file_list - @original_files).first
    assert_match /add_yaffle_fields_to_bird/, new_file

You can run 'rake' from the plugin directory to see this fail.  Unless you are doing more advanced generator commands it typically suffices to just test the Generate script, and trust that rails will handle the Destroy and Update commands for you.

=== Adding to the manifest ===

This example will demonstrate how to use one of the built-in generator methods named 'migration_template' to create a migration file.  To start, update your generator file to look like this:


[source, ruby]
class YaffleGenerator < Rails::Generator::NamedBase
  def manifest
    record do |m|
      m.migration_template 'migration:migration.rb', "db/migrate", {:assigns => yaffle_local_assigns,
        :migration_file_name => "add_yaffle_fields_to_#{custom_file_name}"

    def custom_file_name
      custom_name = class_name.underscore.downcase
      custom_name = custom_name.pluralize if ActiveRecord::Base.pluralize_table_names

    def yaffle_local_assigns
      returning(assigns = {}) do
        assigns[:migration_action] = "add"
        assigns[:class_name] = "add_yaffle_fields_to_#{custom_file_name}"
        assigns[:table_name] = custom_file_name
        assigns[:attributes] = ["last_squawk", "string")]

The generator creates a new file in 'db/migrate' with a timestamp and an 'add_column' statement.  It reuses the built in rails `migration_template` method, and reuses the built-in rails migration template.

It's courteous to check to see if table names are being pluralized whenever you create a generator that needs to be aware of table names.  This way people using your generator won't have to manually change the generated files if they've turned pluralization off.

=== Manually test the generator ===

To run the generator, type the following at the command line:

./script/generate yaffle bird

and you will see a new file:


[source, ruby]
class AddYaffleFieldsToBirds < ActiveRecord::Migration
  def self.up
    add_column :birds, :last_squawk, :string

  def self.down
    remove_column :birds, :last_squawk

=== The USAGE file ===

Rails ships with several built-in generators.  You can see all of the generators available to you by typing the following at the command line:


You should see something like this:

Installed Generators
  Plugins (vendor/plugins): yaffle
  Builtin: controller, integration_test, mailer, migration, model, observer, plugin, resource, scaffold, session_migration

When you run `script/generate yaffle` you should see the contents of your 'vendor/plugins/yaffle/generators/yaffle/USAGE' file.  

For this plugin, update the USAGE file looks like this:

    Creates a migration that adds yaffle squawk fields to the given model

    ./script/generate yaffle hickwall

    This will create: