elucid-rails_admin 0.0.1

data/lib/rails_admin/version.rb

@@ -0,0 +1,6 @@
+module RailsAdmin
+  # FIXME: this needs to be manually kept in sync with the gemspec's
+  # s.version until http://jira.codehaus.org/browse/JRUBY-5319 is
+  # fixed
+  VERSION = "0.0.1"
+end

data/lib/tasks/prepare_ci_env.rake

@@ -0,0 +1,27 @@
+namespace :rails_admin do
+  desc "Prepare Continuous Integration environment"
+  task :prepare_ci_env do
+    ENV['SKIP_RAILS_ADMIN_INITIALIZER'] = 'true'
+    adapter = ENV["CI_DB_ADAPTER"] || "sqlite3"
+    database = ENV["CI_DB_DATABASE"] || ("sqlite3" == adapter ? "db/development.sqlite3" : "ci_rails_admin")
+
+    configuration = {
+      "test" => {
+        "adapter" => adapter,
+        "database" => database,
+        "username" => ENV["CI_DB_USERNAME"],
+        "password" => ENV["CI_DB_PASSWORD"],
+        "host" => ENV["CI_DB_HOST"] || "localhost",
+        "encoding" => ENV["CI_DB_ENCODING"] || "utf8",
+        "pool" => (ENV["CI_DB_POOL"] || 5).to_int,
+        "timeout" => (ENV["CI_DB_TIMEOUT"] || 5000).to_int
+      }
+    }
+
+    filename = Rails.root.join("config/database.yml")
+
+    File.open(filename, "w") do |f|
+      f.write(configuration.to_yaml)
+    end
+  end
+end

data/lib/tasks/rails_admin.rake

@@ -0,0 +1,18 @@
+task :environment => :disable_rails_admin_initializer
+
+task :disable_rails_admin_initializer do
+  ENV['SKIP_RAILS_ADMIN_INITIALIZER'] = 'true' if ENV['SKIP_RAILS_ADMIN_INITIALIZER'].nil?
+end
+
+namespace :rails_admin do
+  desc "Install rails_admin"
+  task :install do
+    system 'rails g rails_admin:install'
+  end
+  
+  desc "Uninstall rails_admin"
+  task :uninstall do
+    system 'rails g rails_admin:uninstall'
+  end
+end
+

data/spec/ci.sh

@@ -0,0 +1,2 @@
+#!/usr/bin/env sh
+cd spec/dummy_app && bundle install --without debug && bundle exec rake rails_admin:prepare_ci_env db:create db:migrate && cd ../.. && bundle exec rake spec

data/spec/controllers/application_controller_spec.rb

@@ -0,0 +1,30 @@
+require 'spec_helper'
+
+describe RailsAdmin::ApplicationController do
+  describe "#to_model_name" do
+    it "handles classes nested in modules of the same name" do
+      controller.to_model_name("conversations~conversations").should eq("Conversations::Conversation")
+    end
+  end
+  
+  describe "helper method _get_plugin_name" do
+    it "works by default" do
+      controller.send(:_get_plugin_name).should == ['Dummy App', 'Admin']
+    end
+    
+    it "works for static names" do
+      RailsAdmin.config do |config|
+        config.main_app_name = ['static','value']
+      end
+      controller.send(:_get_plugin_name).should == ['static', 'value']
+    end
+    
+    it "works for dynamic names in the controller context" do
+      RailsAdmin.config do |config|
+        config.main_app_name = Proc.new { |controller| [Rails.application.engine_name.try(:titleize), controller.params[:action].titleize] }
+      end
+      controller.params[:action] = "dashboard"
+      controller.send(:_get_plugin_name).should == ["Dummy App Application", "Dashboard"]
+    end
+  end
+end

data/spec/controllers/main_controller_spec.rb

@@ -0,0 +1,86 @@
+require 'spec_helper'
+
+describe RailsAdmin::MainController do
+  describe "list_entries for associated_collection" do
+    before do
+      @team = FactoryGirl.create :team      
+      controller.params = { :associated_collection => "players", :current_action => "update", :source_abstract_model => 'teams', :source_object_id => @team.id, :model_name => "players" }
+      controller.get_model # set @model_config for Team
+    end
+    
+    it "doesn't scope associated collection records when associated_collection_scope is nil" do
+      @players = 2.times.map do
+        FactoryGirl.create :player
+      end
+      
+      RailsAdmin.config Team do
+        field :players do
+          associated_collection_scope false
+        end
+      end
+
+      controller.list_entries.length.should == @players.size
+    end
+    
+    it "scopes associated collection records according to associated_collection_scope" do
+      @players = 4.times.map do
+        FactoryGirl.create :player
+      end
+      
+      RailsAdmin.config Team do
+        field :players do
+          associated_collection_scope do
+            Proc.new { |scope| scope.limit(3) }
+          end
+        end
+      end
+      
+      controller.list_entries.length.should == 3
+    end
+    
+    it "scopes associated collection records according to bindings" do
+      @team.revenue = 3
+      @team.save
+      
+      @players = 5.times.map do
+        FactoryGirl.create :player
+      end
+
+      RailsAdmin.config Team do
+        field :players do
+          associated_collection_scope do
+            team = bindings[:object]
+            Proc.new { |scope|
+              scope.limit(team.revenue)
+            }
+          end
+        end
+      end
+
+      controller.list_entries.length.should == @team.revenue
+    end
+    
+    
+    it "limits associated collection records number to 30 if cache_all is false and doesn't otherwise" do
+      @players = 40.times.map do
+        FactoryGirl.create :player
+      end
+      
+      RailsAdmin.config Team do
+        field :players do
+          associated_collection_cache_all false
+        end
+      end
+      controller.list_entries.length.should == 30
+      
+      RailsAdmin.config Team do
+        field :players do
+          associated_collection_cache_all true
+        end
+      end
+      controller.list_entries.length.should == @players.size
+      
+    end
+    
+  end
+end

data/spec/database_helpers.rb

@@ -0,0 +1,15 @@
+module DatabaseHelpers
+
+  def migrate_database
+    silence_stream(STDOUT) do
+      ActiveRecord::Migrator.migrate File.expand_path('../dummy_app/db/migrate/', __FILE__)
+    end
+  end
+
+  def drop_all_tables
+    ActiveRecord::Base.connection.tables.each do |table|
+      ActiveRecord::Base.connection.drop_table(table)
+    end
+  end
+
+end

data/spec/dummy_app/Gemfile

@@ -0,0 +1,52 @@
+source 'http://rubygems.org'
+
+gem 'rails', '~> 3.1'
+gem 'devise', '~> 1.4'
+gem 'rails_admin', :path => '../../'
+gem 'mlb', '~> 0.5'
+gem 'paperclip', '~> 2.4'
+gem 'mini_magick'
+gem 'carrierwave'
+gem 'dragonfly'
+
+# Gems used only for assets and not required
+# in production environments by default.
+group :assets do
+  gem 'sass-rails', '~> 3.1'
+  gem 'coffee-rails', '~> 3.1'
+  gem 'uglifier', '~> 1.0'
+end
+
+group :development, :test do
+  platforms :jruby do
+    gem 'jruby-openssl', '~> 0.7'
+    # activerecord-jdbc-adapter does not yet have a rails 3.1 compatible release
+    gem 'activerecord-jdbc-adapter', :git => 'git://github.com/jruby/activerecord-jdbc-adapter.git'
+    case ENV['CI_DB_ADAPTER']
+    when 'mysql'
+      gem 'activerecord-jdbcmysql-adapter', '~> 1.1'
+      gem 'jdbc-mysql', '~> 5.1'
+    when 'postgresql'
+      gem 'activerecord-jdbcpostgresql-adapter', '~> 1.1'
+      gem 'jdbc-postgres', '~> 9.0'
+    else
+      gem 'activerecord-jdbcsqlite3-adapter', '~> 1.1'
+      gem 'jdbc-sqlite3', '~> 3.6'
+    end
+  end
+
+  platforms :ruby, :mswin, :mingw do
+    case ENV['CI_DB_ADAPTER']
+    when 'mysql'
+      gem 'mysql', '~> 2.8'
+    when 'postgresql'
+      gem 'pg', '~> 0.10'
+    else
+      gem 'sqlite3', '~> 1.3'
+    end
+  end
+end
+
+platforms :jruby, :mingw_18, :ruby_18 do
+  gem 'fastercsv', '~> 1.5'
+end

data/spec/dummy_app/README

@@ -0,0 +1,256 @@
+== 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 i ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.find(: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.com/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
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |   |-- images
+  |   |-- javascripts
+  |   `-- stylesheets
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      `-- plugins
+
+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. 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. 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 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.