acts_as_relation 0.1 → 0.1.1

data/.gitignore

@@ -7,3 +7,4 @@ tmp/*
 doc/*
 *.sqlite3
 *.log
+spec/dummy/tmp/*

data/Gemfile

@@ -1,4 +1,4 @@
-source "http://rubygems.org"
+source "https://rubygems.org"
 
 # Specify your gem's dependencies in acts_as_list-rails3.gemspec
 gemspec

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright 2012 Hassan Zamani
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.rdoc

@@ -80,14 +80,14 @@ On the other hand you can always access a specific object from its parent by cal
 The +acts_as+ relation support these options:
 
 * +:as+
-* +:auto_join+
+* +:auto_include+
 * +:class_name+
 * +:conditions+
 * +:dependent+
 * +:include+
 
-when +:auto_join+ option set to +true+ (wich is by default), every query on child
-will automatically joins with paren. For example:
+when +:auto_join+ option set to +true+ (which is by default), every query on child
+will automatically includes the parent. For example:
 
     Pen.where("name = ?", "somename")
 

data/acts_as_relation.gemspec

@@ -26,6 +26,8 @@ Gem::Specification.new do |s|
   s.add_development_dependency "rake"
   s.add_development_dependency "bundler"
   s.add_development_dependency "sqlite3"
-  s.add_development_dependency "rspec"
+  s.add_development_dependency "rspec-rails"
+  s.add_development_dependency "rails"
+  s.add_development_dependency "database_cleaner"
   s.add_dependency "activerecord"
 end

data/init.rb

@@ -0,0 +1 @@
+require 'acts_as_relation'

data/lib/active_record/acts_as_relation.rb

@@ -9,7 +9,7 @@ module ActiveRecord
       protected
       def define_acts_as_accessors(attribs, model_name)
         attribs.each do |attrib|
-          class_eval <<-EndEval
+          code = <<-EndCode
             def #{attrib}
               #{model_name}.#{attrib}
             end
@@ -21,7 +21,8 @@ module ActiveRecord
             def #{attrib}?
               #{model_name}.#{attrib}?
             end
-          EndEval
+          EndCode
+          class_eval code, __FILE__, __LINE__
         end
       end
     end
@@ -48,7 +49,7 @@ module ActiveRecord
             :conditions => options[:conditions]
           }
 
-          acts_as_model.module_eval <<-EndEval
+          code = <<-EndCode
             def self.included(base)
               base.has_one :#{name}, #{has_one_options}
               base.validate :#{name}_must_be_valid
@@ -87,7 +88,8 @@ module ActiveRecord
                 end
               end
             end
-          EndEval
+          EndCode
+          acts_as_model.module_eval code, __FILE__, __LINE__
         end
 
         class_eval do
@@ -95,10 +97,10 @@ module ActiveRecord
         end
 
         if options.fetch :auto_join, true
-          class_eval "default_scope joins(:#{name})"
+          class_eval "default_scope joins(:#{name}).readonly(false)"
         end
 
-        instance_eval <<-EndEval
+        code = <<-EndCode
           def acts_as_other_model?
             true
           end
@@ -106,21 +108,23 @@ module ActiveRecord
           def acts_as_model_name
             :#{name}
           end
-        EndEval
+        EndCode
+        instance_eval code, __FILE__, __LINE__
       end
       alias :is_a :acts_as
 
-      def acts_as_superclass
-        association_name = acts_as_association_name
+      def acts_as_superclass options={}
+        association_name = options[:as] || acts_as_association_name
 
-        class_eval <<-EndEval
+        code = <<-EndCode
           belongs_to :#{association_name}, :polymorphic => true
 
           def specific
             self.#{association_name}
           end
           alias :specific_class :specific
-        EndEval
+        EndCode
+        class_eval code, __FILE__, __LINE__
       end
       alias :is_a_superclass :acts_as_superclass
 

data/lib/version.rb

@@ -1,5 +1,5 @@
 module ActiveRecord
   module ActsAsRelation
-    VERSION = "0.1"
+    VERSION = "0.1.1"
   end
 end

data/spec/{acts_as_relation/acts_as_relation_spec.rb → acts_as_relation_spec.rb}

@@ -1,10 +1,6 @@
 require 'spec_helper'
 
 describe "Submodel" do
-  before :all do
-    ActsAsRelationSchema.migrate
-  end
-
   it "inherits Supermodel attributes" do
     pen = Pen.new
     ['name', 'name=', 'name_changed?', 'name_was',
@@ -43,6 +39,13 @@ describe "Submodel" do
     pen.parent_method.should == "RedPen - 0.8"
   end
 
+  # it "inherits Supermodel dynamic finders" do
+  #   pending
+  #   pen = Pen.create :name => 'RedPen'
+  #   product = Product.create :name => 'SomeProduct'
+  #   Product.find_by_name('SomeProduct').should == product
+  # end
+
   it "should raise NoMethodEror on unexisting method calls" do
     pen = Pen.create :name => 'RedPen', :price => 0.8, :color => 'red'
     lambda { pen.unexisted_method }.should raise_error(NoMethodError)
@@ -67,6 +70,18 @@ describe "Submodel" do
     end
   end
 
+  it "should be findable" do
+    pen = Pen.create :name => 'RedPen', :price => 0.8, :color => 'red'
+    pen = Pen.find(pen.id)
+    pen.should be_valid
+  end
+
+  it "should be saveable" do
+    pen = Pen.create :name => 'RedPen', :price => 0.8, :color => 'red'
+    pen = Pen.find(pen.id)
+    lambda { pen.save }.should_not raise_error
+  end
+
   describe "Query Interface" do
     describe "auto_join" do
       it "automaticaly joins Supermodel on Submodel queries" do

data/spec/acts_as_superclass_spec.rb

@@ -0,0 +1,14 @@
+require 'spec_helper'
+
+describe "create_table acts_as_superclass" do
+  it "creates foreign key and type columns" do
+    name = Pen.acts_as_association_name
+    Pen.attribute_names.should include("#{name}_id")
+    Pen.attribute_names.should include("#{name}_type")
+  end
+
+  it "when name passed creates foreign key and type columns with given name" do
+    Product.attribute_names.should include("producible_id")
+    Product.attribute_names.should include("producible_type")
+  end
+end

data/spec/dummy/.rspec

@@ -0,0 +1 @@
+--colour

data/spec/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+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, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. 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.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, 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 can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. 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.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |       |-- images
+  |       |-- javascripts
+  |       `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+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. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+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.html.erb.
+  Inside default.html.erb, 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 generators 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.
+
+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. 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 rails generate
+  command, 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. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.