aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test
Commit message (Collapse)AuthorAgeFilesLines
* Ensure asset_path defaults to nil for applicationJosé Valim2010-12-091-0/+5
|
* Rails::Engine.find(path) - method to find engine by pathPiotr Sarnacki2010-12-091-0/+19
|
* Rake tasks for managing database while development and testing of enginesPiotr Sarnacki2010-12-091-1/+1
| | | | | | | | | | | | Some of the engines needs database. As engine needs to be run inside Rails application, migrations and other database operations are run from dummy application. To make that process simple I changed db tasks to look for migrations in both engine's and application's db/migrate directory. You can run all of the database tasks from test/dummy or directly from engine with prefix app, like: rake app:db:migrate rake app:db:migrate:redo
* Application templates should work with HTTPS tooMikel Lindsaar2010-11-271-0/+9
|
* Do not create table_name_prefix method on isolated module if the method ↵Piotr Sarnacki2010-11-221-0/+19
| | | | | | already exists. Signed-off-by: José Valim <jose.valim@gmail.com>
* Ensure that initializers are executed before loading rake tasksPiotr Sarnacki2010-11-181-0/+16
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Facepunch failing tests.José Valim2010-11-182-9/+9
|
* Add config.action_controller.include_all_helpers, by default it is set to true.Piotr Sarnacki2010-11-181-0/+60
| | | | | | | In older rails versions there was a way to use only helpers from helper file corresponding to current controller and you could also include all helpers by saying 'helper :all' in controller. This config allows to return to older behavior by setting it to false.
* Tidy up generators commits.José Valim2010-11-172-11/+8
|
* Fix generators tests on ruby 1.9Piotr Sarnacki2010-11-171-6/+8
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Fix plugin new --mountable: ActionController instead of ActiveControllerPiotr Sarnacki2010-11-161-1/+1
|
* Fix misspelling of 'deprecation' in plugin_generator.Doug Ireton2010-11-161-1/+1
|
* Fix failing tests.José Valim2010-11-161-29/+7
|
* Do not allow to use plugin_new generator directly, you should use Usage:Piotr Sarnacki2010-11-161-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | rails new APP_PATH [options] Options: -G, [--skip-git] # Skip Git ignores and keeps -r, [--ruby=PATH] # Path to the Ruby binary of your choice # Default: /Users/drogus/.rvm/rubies/ruby-1.8.7-p302/bin/ruby -b, [--builder=BUILDER] # Path to an application builder (can be a filesystem path or URL) [--edge] # Setup the application with Gemfile pointing to Rails repository [--dev] # Setup the application with Gemfile pointing to your Rails checkout [--skip-gemfile] # Don't create a Gemfile -d, [--database=DATABASE] # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db) # Default: sqlite3 -O, [--skip-active-record] # Skip Active Record files -m, [--template=TEMPLATE] # Path to an application template (can be a filesystem path or URL) -J, [--skip-prototype] # Skip Prototype files -T, [--skip-test-unit] # Skip Test::Unit files Runtime options: -s, [--skip] # Skip files that already exist -p, [--pretend] # Run but do not make any changes -f, [--force] # Overwrite files that already exist -q, [--quiet] # Supress status output Rails options: -v, [--version] # Show Rails version number and quit -h, [--help] # Show this help message and quit Description: The 'rails new' command creates a new Rails application with a default directory structure and configuration at the path you specify. Example: rails new ~/Code/Ruby/weblog This generates a skeletal Rails installation in ~/Code/Ruby/weblog. See the README in the newly created application to get going. command
* Allow running `rails plugin new` command inside rails applicationPiotr Sarnacki2010-11-161-0/+6
|
* Deprecate plugin generatorPiotr Sarnacki2010-11-161-6/+12
|
* Add skip-gemspec option to 'plugin new' generatorPiotr Sarnacki2010-11-161-0/+5
|
* Remove whitespaces and add missing test.José Valim2010-11-112-6/+12
|
* Merge remote branch 'drogus/plugin_new'José Valim2010-11-1115-167/+614
|\ | | | | | | | | Conflicts: railties/test/generators/app_generator_test.rb
| * Allow to set dummy application path through optionsPiotr Sarnacki2010-11-081-0/+7
| |
| * Fix scaffold generator to be aware of namespace in isolated enginePiotr Sarnacki2010-11-031-0/+153
| |
| * Add --mountable option to 'plugin new' generator which generates full ↵Piotr Sarnacki2010-11-021-0/+9
| | | | | | | | mountable application (engine)
| * Add example rake task to 'plugin new' generatorPiotr Sarnacki2010-11-021-0/+1
| |
| * create_dummy_app method that allows to easily create dummy application from ↵Piotr Sarnacki2010-11-023-5/+19
| | | | | | | | template
| * Properly skip test unit in 'plugin new' generatorPiotr Sarnacki2010-11-022-5/+5
| |
| * Properly handle other databases in 'plugin new' generatorPiotr Sarnacki2010-11-023-5/+22
| |
| * Skip active record properly in 'plugin new' generatorPiotr Sarnacki2010-11-021-0/+1
| |
| * Use rails integration tests by default in 'plugin new' generatorPiotr Sarnacki2010-11-021-3/+1
| |
| * Make deep copy of application generators on engine initialization.Piotr Sarnacki2010-11-021-0/+3
| | | | | | | | | | Otherwise nested hashes will be same objects for both application and engine, which will result in overwriting each others values on changes.
| * Use application's generators defaults as engine defaults to not force users ↵Piotr Sarnacki2010-11-021-0/+17
| | | | | | | | to manually set it
| * Don't be verbose while creating dummy application in plugin new generatorPiotr Sarnacki2010-11-021-0/+4
| |
| * Pass more options to test/dummy in 'plugin new' generatorPiotr Sarnacki2010-11-021-0/+15
| |
| * Add --full option to 'plugin new' generator, which generates rails enginePiotr Sarnacki2010-11-021-1/+27
| |
| * No need for say_step in 'plugin new' generatorPiotr Sarnacki2010-11-021-4/+3
| |
| * Remove integration tests and ActionModel/ActiveRecord calls from 'rake ↵Piotr Sarnacki2010-11-022-8/+2
| | | | | | | | plugin new' generator, it shouldn't be available as default option
| * Make tests for app and plugin generators more DRYPiotr Sarnacki2010-11-028-287/+219
| |
| * Allow easy overriding of test framework in 'rake plugin new' generator, ↵Piotr Sarnacki2010-11-022-0/+23
| | | | | | | | using PluginBuilder
| * Ensure that tests run properlyPiotr Sarnacki2010-11-021-0/+7
| |
| * Change // style regexp to %r{}, to not confuse editors code highlightingPiotr Sarnacki2010-11-021-1/+1
| |
| * Add --dev and --edge options to rails plugin newPiotr Sarnacki2010-11-021-0/+13
| |
| * Add support for templates for rails plugin newPiotr Sarnacki2010-11-021-0/+20
| |
| * Ensure that options for plugin new generator are not passed to application ↵Piotr Sarnacki2010-11-021-0/+6
| | | | | | | | generator
| * Added 'rails plugin new' generator which generates gem plugin skeleton.Piotr Sarnacki2010-11-024-0/+195
| | | | | | | | | | | | This command is based on enginex gem by José Valim. It generates gem structure and ads dummy application into test/dummy. This can be used to start developing any kind of extension for rails 3.
* | skip testing framework if app created with --skip-test-unit [#5796 ↵Rob Zolkos2010-11-111-0/+7
| | | | | | | | | | | | state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* | The model generator shouldn't throw warnings when using mass nouns [#5363 ↵Jeff Kreeftmeijer2010-11-111-0/+5
| | | | | | | | | | | | state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* | Strip regexp anchors from rake routes output [#5934 state:resolved]Andrew White2010-11-091-0/+9
|/
* Remove task for creating symlinks for railtiesPiotr Sarnacki2010-10-141-57/+0
|
* Add task foo:install (where foo is plugin) as a shortcutinstall:migrations ↵Piotr Sarnacki2010-10-141-0/+24
| | | | and foo:install:assets
* Added foo:install:assets task that copies assets from plugins public ↵Piotr Sarnacki2010-10-141-0/+14
| | | | | | | | | | | directory to application's public directory This is the most simple and naive approach: just copy every files from engine to app. The only exception is when file has changed, in that case developer will be asked if he wants to rename the field. There is no need to make this task more sophisticated as 3.1 will be shipped with better assets handling and it will be the default way to handle things.
* Do not treat information about skipped migrations as WARNINGs but as a ↵Piotr Sarnacki2010-10-141-5/+5
| | | | NOTEs, also puts to stdin
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-08 04:30:58 +0000