has_many_polymorphs 2.2 → 2.9

data/Rakefile

@@ -1,28 +0,0 @@
-
-require 'echoe'
-
-Echoe.new("has_many_polymorphs") do |p|  
-  p.project = "fauna"
-  p.summary = "An ActiveRecord plugin for self-referential and double-sided polymorphic associations."
-  p.url = "http://blog.evanweaver.com/files/doc/fauna/has_many_polymorphs/"  
-  p.docs_host = "blog.evanweaver.com:~/www/bax/public/files/doc/"  
-  p.dependencies = ["activerecord"]
-  p.rdoc_pattern = /polymorphs\/association|polymorphs\/class_methods|polymorphs\/reflection|polymorphs\/autoload|polymorphs\/configuration|README|CHANGELOG|TODO|LICENSE|templates\/migration\.rb|templates\/tag\.rb|templates\/tagging\.rb|templates\/tagging_extensions\.rb/    
-  p.require_signed = true
-  p.clean_pattern += ["**/ruby_sess*", "**/generated_models/**"]
-  p.test_pattern = ["test/unit/*_test.rb", "test/integration/*_test.rb", "test/generator/*_test.rb"]
-end
-
-desc "Run all the tests for every database adapter" 
-task "test_all" do
-  ['mysql', 'postgresql', 'sqlite3'].each do |adapter|
-    ENV['DB'] = adapter
-    ENV['PRODUCTION'] = nil
-    STDERR.puts "#{'='*80}\nDevelopment mode for #{adapter}\n#{'='*80}"
-    system("rake test:multi_rails:all")
-  
-    ENV['PRODUCTION'] = '1'
-    STDERR.puts "#{'='*80}\nProduction mode for #{adapter}\n#{'='*80}"
-    system("rake test:multi_rails:all")    
-  end
-end

data/examples/hmph.rb

@@ -1,69 +0,0 @@
-require 'camping'
-require 'has_many_polymorphs'
-
-Camping.goes :Hmph
-
-module Hmph::Models
-  class GuestsKennel < Base
-    belongs_to :kennel
-    belongs_to :guest, :polymorphic => true
-  end
-
-  class Dog < Base
-  end
-
-  class Cat < Base
-  end
-
-  class Bird < Base
-  end
-  
-  class Kennel < Base
-    has_many_polymorphs :guests, 
-      :from => [:dogs, :cats, :birds],
-      :through => :guests_kennels,
-      :namespace => :"hmph/models/"      
-  end  
-
-  class InitialSchema < V 1.0
-    def self.up
-      create_table :hmph_kennels do |t|
-        t.column :created_at, :datetime
-        t.column :modified_at, :datetime
-        t.column :name, :string, :default => 'Anonymous Kennel'
-      end
-
-      create_table :hmph_guests_kennels do |t|
-        t.column :guest_id, :integer
-        t.column :guest_type, :string
-        t.column :kennel_id, :integer
-      end
-
-      create_table :hmph_dogs do |t|
-        t.column :name, :string, :default => 'Fido'
-      end
-
-      create_table :hmph_cats do |t|
-        t.column :name, :string, :default => 'Morris'
-      end
-
-      create_table :hmph_birds do |t|
-        t.column :name, :string, :default => 'Polly'
-      end
-    end
-
-    def self.down
-      drop_table :hmph_kennels
-      drop_table :hmph_guests_kennels
-      drop_table :hmph_dogs
-      drop_table :hmph_cats
-      drop_table :hmph_birds
-    end
-  end
-end
-
-module Hmph::Controllers
-end
-
-module Hmph::Views
-end

data/lib/has_many_polymorphs/configuration.rb

@@ -1,19 +0,0 @@
-
-=begin rdoc
-Access the <tt>has_many_polymorphs_options</tt> hash in your Rails::Initializer.run#after_initialize block if you need to modify the behavior of Rails::Initializer::HasManyPolymorphsAutoload.
-=end
-
-module Rails #:nodoc:
-  class Configuration
-
-    def has_many_polymorphs_options
-      ::HasManyPolymorphs.options
-    end
-    
-    def has_many_polymorphs_options=(hash)
-      ::HasManyPolymorphs.options = HashWithIndifferentAccess.new(hash)
-    end
-    
-  end  
-end
-

data/test/fixtures/people.yml

@@ -1,7 +0,0 @@
-bob:
-  id: 1
-  name: Bob 
-  age: 45
-  created_at: "2007-04-01 12:00:00"
-  updated_at: "2007-04-04 10:00:00"
-  

data/test/generator/tagging_generator_test.rb

@@ -1,42 +0,0 @@
-require 'fileutils'
-require File.dirname(__FILE__) + '/../test_helper'
-
-class TaggingGeneratorTest < ActiveSupport::TestCase
-  
-  def setup
-    Dir.chdir RAILS_ROOT do
-      truncate
-
-      # Revert environment lib requires
-      FileUtils.cp "config/environment.rb.canonical", "config/environment.rb"
-      
-      # Delete generator output
-      ["app/models/tag.rb", "app/models/tagging.rb", 
-        "test/unit/tag_test.rb", "test/unit/tagging_test.rb", 
-        "test/fixtures/tags.yml", "test/fixtures/taggings.yml",
-        "lib/tagging_extensions.rb",
-        "db/migrate/010_create_tags_and_taggings.rb"].each do |file|
-          File.delete file if File.exist? file
-      end
-      
-      # Rebuild database
-      Echoe.silence do
-        system("ruby #{HERE}/setup.rb")
-      end
-    end
-  end
-  
-  alias :teardown :setup
-
-  def test_generator
-    Dir.chdir RAILS_ROOT do
-      Echoe.silence do
-        assert system("script/generate tagging Stick Stone -q -f")
-        assert system("rake db:migrate")
-        assert system("rake db:fixtures:load")
-        assert system("rake test:units")      
-      end
-    end
-  end
-  
-end

data/test/integration/app/README

@@ -1,182 +0,0 @@
-== Welcome to Rails
-
-Rails is a web-application and persistence framework that includes everything
-needed to create database-backed web-applications according to the
-Model-View-Control pattern of separation. This pattern splits the view (also
-called the presentation) into "dumb" templates that are primarily responsible
-for inserting pre-built data in between HTML tags. The model contains the
-"smart" domain objects (such as Account, Product, Person, Post) that holds all
-the business logic and knows how to persist themselves to a database. The
-controller handles the incoming requests (such as Save New Account, Update
-Product, Show Post) by manipulating the model and directing data to the view.
-
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
-
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails.  You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
-
-
-== Getting started
-
-1. At the command prompt, start a new rails application using the rails command
-   and your application name. Ex: rails myapp
-   (If you've downloaded rails in a complete tgz or zip, this step is already done)
-2. Change directory into myapp and start the web server: <tt>script/server</tt> (run with --help for options)
-3. Go to http://localhost:3000/ and get "Welcome aboard: You’re riding the Rails!"
-4. Follow the guidelines to start developing your application
-
-
-== Web Servers
-
-By default, Rails will try to use Mongrel and lighttpd if they are installed, otherwise
-Rails will use the WEBrick, the webserver that ships with Ruby. When you run script/server,
-Rails will check if Mongrel exists, then lighttpd and finally fall back to WEBrick. This ensures
-that you can always get up and running quickly.
-
-Mongrel is a Ruby-based webserver with a C-component (which requires compilation) that is
-suitable for development and deployment of Rails applications. If you have Ruby Gems installed,
-getting up and running with mongrel is as easy as: <tt>gem install mongrel</tt>.
-More info at: http://mongrel.rubyforge.org
-
-If Mongrel is not installed, Rails will look for lighttpd. It's considerably faster than
-Mongrel and WEBrick and also suited for production use, but requires additional
-installation and currently only works well on OS X/Unix (Windows users are encouraged
-to start with Mongrel). We recommend version 1.4.11 and higher. You can download it from
-http://www.lighttpd.net.
-
-And finally, if neither Mongrel or lighttpd are installed, Rails will use the built-in Ruby
-web server, WEBrick. WEBrick is a small Ruby web server suitable for development, but not
-for production.
-
-But of course its also possible to run Rails on any platform that supports FCGI.
-Apache, LiteSpeed, IIS are just a few. For more information on FCGI,
-please visit: http://wiki.rubyonrails.com/rails/pages/FastCGI
-
-
-== Debugging Rails
-
-Have "tail -f" commands running on the server.log and development.log. Rails will
-automatically display debugging and runtime information to these files. Debugging
-info will also be shown in the browser on requests from 127.0.0.1.
-
-
-== Breakpoints
-
-Breakpoint support is available through the script/breakpointer client. This
-means that you can break out of execution at any point in the code, investigate
-and change the model, AND then resume execution! Example:
-
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.find(:all)
-      breakpoint "Breaking out from the list"
-    end
-  end
-
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the breakpointer window. Here you can do things like:
-
-Executing breakpoint "Breaking out from the list" at .../webrick_server.rb:16 in 'breakpoint'
-
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>,
-       #<Post:0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
-  >> @posts.first.title = "hello from a breakpoint"
-  => "hello from a breakpoint"
-
-...and even better is that you can examine how your runtime objects actually work:
-
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-
-Finally, when you're ready to resume execution, you press CTRL-D
-
-
-== Console
-
-You can interact with the domain model by starting the console through <tt>script/console</tt>.
-Here you'll have all parts of the application configured, just like it is when the
-application is running. You can inspect domain models, change values, and save to the
-database. Starting the script without arguments will launch it in the development environment.
-Passing an argument will specify a different environment, like <tt>script/console production</tt>.
-
-To reload your controllers and models after launching the console run <tt>reload!</tt>
-
-To reload your controllers and models after launching the console run <tt>reload!</tt>
-
-
-
-== Description of contents
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from ApplicationController
-  which itself descends from ActionController::Base.
-
-app/models
-  Holds models that should be named like post.rb.
-  Most models will descend from ActiveRecord::Base.
-
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.rhtml for the WeblogsController#index action. All views use eRuby
-  syntax.
-
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the common
-  header/footer method of wrapping views. In your views, define a layout using the
-  <tt>layout :default</tt> and create a file named default.rhtml. Inside default.rhtml,
-  call <% yield %> to render the view using this layout.
-
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are generated
-  for you automatically when using script/generate for controllers. Helpers can be used to
-  wrap functionality for your views into methods.
-
-config
-  Configuration files for the Rails environment, the routing map, the database, and other dependencies.
-
-components
-  Self-contained mini-applications that can bundle together controllers, models, and views.
-
-db
-  Contains the database schema in schema.rb.  db/migrate contains all
-  the sequence of Migrations for your schema.
-
-doc
-  This directory is where your application documentation will be stored when generated
-  using <tt>rake doc:app</tt>
-
-lib
-  Application specific libraries. Basically, any kind of custom code that doesn't
-  belong under controllers, models, or helpers. This directory is in the load path.
-
-public
-  The directory available for the web server. Contains subdirectories for images, stylesheets,
-  and javascripts. Also contains the dispatchers and the default HTML files. This should be
-  set as the DOCUMENT_ROOT of your web server.
-
-script
-  Helper scripts for automation and generation.
-
-test
-  Unit and functional tests along with fixtures. When using the script/generate scripts, template
-  test files will be generated for you and placed in this directory.
-
-vendor
-  External libraries that the application depends on. Also includes the plugins subdirectory.
-  This directory is in the load path.

data/test/integration/app/Rakefile

@@ -1,19 +0,0 @@
-# Add your own tasks in files placed in lib/tasks ending in .rake,
-# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
-
-require(File.join(File.dirname(__FILE__), 'config', 'boot'))
-
-require 'rake'
-require 'rake/testtask'
-require 'rake/rdoctask'
-
-require 'tasks/rails'
-
-namespace :test do
-  desc "a new rake task to include generators"
-  Rake::TestTask.new(:generators) do |t|
-    t.libs << 'lib'
-    t.test_files = FileList['test/generators/*_test.rb']
-    t.verbose = true
-  end
-end

data/test/integration/app/app/controllers/application.rb

@@ -1,7 +0,0 @@
-# Filters added to this controller apply to all controllers in the application.
-# Likewise, all the methods added will be available for all controllers.
-
-class ApplicationController < ActionController::Base
-  # Pick a unique cookie name to distinguish our session data from others'
-  session :session_key => '_testapp_session_id'
-end

data/test/integration/app/app/controllers/bones_controller.rb

@@ -1,5 +0,0 @@
-class BonesController < ApplicationController
-  def index
-    @bones = Bone.find(:all)  
-  end
-end

data/test/integration/app/app/helpers/addresses_helper.rb

@@ -1,2 +0,0 @@
-module AddressesHelper
-end

data/test/integration/app/app/helpers/application_helper.rb

@@ -1,3 +0,0 @@
-# Methods added to this helper will be available to all templates in the application.
-module ApplicationHelper
-end

data/test/integration/app/app/helpers/bones_helper.rb

@@ -1,2 +0,0 @@
-module BonesHelper
-end

data/test/integration/app/app/helpers/sellers_helper.rb

@@ -1,28 +0,0 @@
-module SellersHelper
-
-  def display_address(seller)
-    logger.info "Seller Data ===================="
-    logger.info seller.inspect
-    logger.info "Seller responds to address " + seller.respond_to?("address").to_s
-    logger.info "Seller responds to address= " + seller.respond_to?("address=").to_s
-    # logger.info seller.methods.sort.inspect
-    logger.info "User Data ===================="
-    logger.info seller.user.inspect
-    logger.info "User responds to address " + seller.user.respond_to?("address").to_s
-    logger.info "User responds to address= " + seller.user.respond_to?("address=").to_s
-    # logger.info seller.user.methods.sort.inspect
-    display_address = Array.new
-    if seller.address
-      display_address << seller.address.city if seller.address.city
-      display_address << seller.address.state.abbreviation if seller.address.state && seller.address.state.abbreviation
-      display_address << seller.address.zip_postal_code if seller.address.zip_postal_code
-    end
-    
-    unless display_address.empty?
-      "Location: " + display_address.join(", ")
-    else
-      "Location: unknown"
-    end
-  end
-  
-end

data/test/integration/app/app/helpers/states_helper.rb

@@ -1,2 +0,0 @@
-module StatesHelper
-end

data/test/integration/app/app/helpers/users_helper.rb

@@ -1,2 +0,0 @@
-module UsersHelper
-end

data/test/integration/app/app/models/bone.rb

@@ -1,2 +0,0 @@
-class Bone < OrganicSubstance
-end

data/test/integration/app/app/models/double_sti_parent.rb

@@ -1,2 +0,0 @@
-class DoubleStiParent < ActiveRecord::Base
-end