aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/generators
Commit message (Collapse)AuthorAgeFilesLines
* Enable wrap_parameter by default in rails api applicationsJorge Bejar2015-06-111-3/+1
|
* Add rake-cors gem (commented) in Gemfile for rails api appsJorge Bejar2015-06-111-0/+3
|
* Add AMS 0.10.0.rc1 by default for api appsSantiago Pastorino2015-06-111-0/+1
|
* Fix scaffold generator test for resource routesSantiago Pastorino2015-06-111-1/+1
|
* Api only apps should include tmp and vendor foldersJorge Bejar2015-06-111-0/+2
|
* Routes resources avoid :new and :edit endpoints if api_only is enabledJorge Bejar2015-06-111-6/+0
|
* Disable jbuilder for Rails API apps, meanwhile it doesn't play nicelySantiago Pastorino2015-06-111-0/+1
|
* Add config.api_only = true to config/application.rb when using rails new --apiSantiago Pastorino2015-06-111-0/+4
|
* Do not generate lib/assets directory for api appsSantiago Pastorino2015-06-111-1/+1
|
* Api apps scaffold does not generate assetsSantiago Pastorino2015-06-111-1/+6
|
* Api apps scaffold does not generate helpersSantiago Pastorino2015-06-111-1/+4
|
* Api apps scaffold does not generate viewsSantiago Pastorino2015-06-111-1/+8
|
* Add api scaffold test for route, controller and its testsSantiago Pastorino2015-06-111-0/+55
|
* API apps scaffold generator generates an apropriate controllerSantiago Pastorino2015-06-111-0/+47
|
* Api apps scaffold generates routes without new and edit actionsSantiago Pastorino2015-06-111-0/+6
|
* Do not generate test/helpers directory for api appsSantiago Pastorino2015-06-111-0/+1
|
* Do not generate app/views directory for api appsSantiago Pastorino2015-06-111-0/+1
|
* Do not generate app/helpers directory for api appsSantiago Pastorino2015-06-111-0/+1
|
* Do not generate app/assets directory for api appsSantiago Pastorino2015-06-111-1/+2
|
* Generate appropriate initializers for an api appSantiago Pastorino2015-06-111-1/+8
|
* rails new --api generates an api app skeletonSantiago Pastorino2015-06-111-0/+76
|
* add option to avoid generating scaffold.cssmasarakki2015-06-091-0/+14
|
* Removed duplicate test cases for template execution Ronak Jangir2015-06-041-9/+0
|
* Merge pull request #20387 from y-yagi/fix_engine_generated_controller_testYves Senn2015-06-022-0/+25
|\ | | | | | | set engine's route in the functional test is generated in the engine
| * add test to run generated test files inside mountable engineyuuji.yaginuma2015-06-023-16/+25
| |
| * add engine's namespace to fixture nameyuuji.yaginuma2015-05-311-0/+1
| |
| * set engine's route in the functional test is generated in the engineyuuji.yaginuma2015-05-311-0/+15
| |
* | Removed use of mocha from railties actions_testRonak Jangir2015-06-011-27/+52
|/
* Generate a `.keep` file in `tmp` folderYoong Kang Lim2015-05-301-0/+27
| | | | | | | | | | | | | A lot of scripts assumes the existence of this folder and most would fail if it is absent. One example of this is `rake restart` (before the previous commit) – it tries to `touch tmp/restart.txt`, which would fail if `tmp` does not exist, which was the case for a freshly-cloned project as `tmp` is `.gitignored` by default. See #20299. [Yoong Kang Lim, Sunny Juneja]
* Omit .keep in .gitignore when generated with --skip-keeps.Ben Pickles2015-05-221-1/+5
|
* list reserved words in generator errorSean Linsley2015-05-052-2/+2
|
* Remove use of mocha in the named base testsSemyon Pupkov2015-04-281-10/+13
|
* Implicitly skip spring for `rails new --dev`Godfrey Chan2015-04-201-0/+8
| | | | | | Spring seems like an obvious foot gun for the `--dev` setup, presumably you are about to make lots of changes to the codebase, so it should always reload the framework.
* fix indent in routes when using namespaced controllersyuuji.yaginuma2015-04-141-1/+3
| | | | | | | | | | | | | | | | | | Before: namespace :foo do namespace :bar do get 'baz/index' end end After: namespace :foo do namespace :bar do get 'baz/index' end end
* Merge pull request #19034 from jvanbaarsen/explicit-job-base-classMatthew Draper2015-03-302-3/+9
|\ | | | | | | Add explicit base class for ActiveJob jobs
| * Add explicit base class for ActiveJob jobsJeroen van Baarsen2015-03-232-3/+9
| | | | | | | | | | | | | | | | * Jobs generated now inherent from ApplicationJob * ApplicationJob inherents from ActiveJob::Base * Added entry to changelog Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
* | respect `pluralize_table_names` when generate fixture file. fixes #19519yuuji.yaginuma2015-03-271-0/+10
| |
* | method_source needs to be a hard dependency on railtiesArthur Neves2015-03-191-7/+0
| |
* | Add a new-line to the end of route method generated code.Arthur Neves2015-03-181-0/+24
|/ | | | | | | | Fix regression on route method that was added by bac812a7ef2660a2fe2ab00822e5e66228379822. The regression was that when calling the `route` method, we were not appending a \n anymore. [fixes #19316]
* add mailer suffix to comments for email previewsyuuji.yaginuma2015-03-151-5/+5
|
* Require `belongs_to` by default.Josef Šimánek2015-02-211-0/+33
| | | | Deprecate `required` option in favor of `optional` for belongs_to.
* Merge pull request #18393 from y-yagi/fix_mailerRafael Mendonça França2015-02-182-16/+25
|\ | | | | follow up to #18074
| * follow up to #18074yuuji.yaginuma2015-01-082-16/+25
| | | | | | | | | | * ignore mailer suffix when generate test files * add mailer suffix to view files
* | Dont check bundler output on plugin generator testArthur Neves2015-02-101-4/+2
| |
* | Actually fix the buildSean Griffin2015-02-101-1/+1
| | | | | | | | Like for real this time. I checked.
* | Fix the buildSean Griffin2015-02-101-1/+1
| |
* | tests, reset global to previous value.Yves Senn2015-02-091-1/+3
| | | | | | | | | | The default of the global might change. It's better to reset it to what it was than a hardcoded value.
* | Remove warning from generator named base testYuki Nishijima2015-02-081-10/+0
| | | | | | | | | | | | | | | | | | This removes the following warning: railties/test/generators/named_base_test.rb:9: warning: method redefined; discarding old pluralize_table_names activesupport/lib/active_support/core_ext/class/attribute.rb:86: warning: previous definition of pluralize_table_names was here railties/test/generators/named_base_test.rb:9: warning: method redefined; discarding old pluralize_table_names= activesupport/lib/active_support/core_ext/class/attribute.rb:83: warning: previous definition of pluralize_table_names= was here
* | README.rdoc -> README.md for newly generated applicationsXavier Noria2015-02-062-3/+3
| | | | | | | | | | | | README.rdoc was generated to support the doc:app task. Now that this task is gone we can switch to Markdown, which is nowadays a better default.
* | Remove documentation tasksXavier Noria2015-02-061-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch removes the tasks doc:app, doc:rails, and doc:guides. In our experience applications do not generate APIs using doc:app. Methods may be certainly documented for maintainers, annotated with YARD tags, etc. but that is intended to be read with the source code, not in a separate website. Then, teams also have typically selected topics written down in Markdown files, or in a GitHub wiki... that kind of thing. If a team absolutely needs to generate application documentation for internal purposes, they can still easily write their own task. Regarding doc:rails and doc:guides, we live in 2015. We are used to go to online docs all the time. If you really want access to the API offline RubyGems generates it for every Rails component unless you tell it not to, and you can checkout the Rails source code to read the guides as Markdown, or download them for a Kindle reader. All in all, maintaining this code does not seem to be worthwhile anymore. As a consequence of this, guides (+3 MB uncompressed) won't be distributed with the rails gem anymore. Of course, guides and API are going to be still part of releases, since documentation is maintained alongside code and tests. Also, time permitting, this will allow us to experiment with novel ways to generate documentation in the Rails docs server, since right now we were constrained by being able to generate them in the user's environment.