aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/generators/plugin_generator_test.rb
Commit message (Collapse)AuthorAgeFilesLines
* Updated tests for the generated version number changeDaniel Morris2015-08-161-3/+3
|
* Merge pull request #21043 from ↵Rafael Mendonça França2015-08-061-0/+1
|\ | | | | | | | | y-yagi/loading_fixtures_in_engine_integration_tests set the correct path to `ActionDispatch::IntegrationTest.fixture_path`
| * set the correct path to `ActionDispatch::IntegrationTest.fixture_path`yuuji.yaginuma2015-07-281-0/+1
| | | | | | | | | | `ActionDispatch::IntegrationTest.fixture_path` set by `test_help.rb`, but if the engine, path under the dummy is will be set, fixtures under test was not loaded.
* | Enable the `api_only` option for API plugins' generatorsRobin Dupret2015-07-231-0/+26
| | | | | | | | | | | | | | This way, running a generator inside the plugin's directory, files that are not relevant won't be generated (e.g. views or assets). This won't interfere with the application's generators configuration.
* | Generate an API dummy application for API pluginsRobin Dupret2015-07-231-0/+8
| |
* | Make ApplicationController inherit from AC::API for API pluginsRobin Dupret2015-07-231-0/+8
| |
* | Skip assets, helpers and views generation for API pluginsRobin Dupret2015-07-231-0/+12
|/
* Display a more human readable list of reserved namesRobin Dupret2015-07-011-1/+1
| | | | | Interpolating an array inside a String will call #inspect on it. Let's call #join to display a more human-readable error message.
* list reserved words in generator errorSean Linsley2015-05-051-1/+1
|
* 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
|
* Fixed a few things from ee9e4c3Godfrey Chan2015-01-301-7/+7
| | | | | Mostly cosmetics, except that `isolate_namespace` should be applied to the last module in the chain.
* Allow hyphenated names for `rails plugin new` generator.Robin Böning2015-01-301-4/+102
| | | | | | It was not possible to create a new gem with a hyphenated name via the `rails plugin new` generator. The naming guide of rubygems clearly says dashes should be used for gems that extend other gems. http://guides.rubygems.org/name-your-gem/
* Change option description and update test namesMelanie Gilman2015-01-291-1/+1
|
* Update option to skip test in generatorsMelanie Gilman2015-01-271-4/+4
| | | | Rails no longer generates Test::Unit files by default.
* Remove debugger supportRafael Mendonça França2015-01-041-3/+0
| | | | | bebugger doesn't work with Ruby 2.2 so we don't need to support it anymore
* Add --skip-action-mailer (or -M) to rails generateclaudiob2015-01-011-0/+28
|
* Skip byebug on all non-MRI rubies, fix testsSean Griffin2014-12-221-1/+1
| | | | | | The changes in #18149 added tests for the app generator, but only fixed it for the plugin generator (I should have let CI finish though I think it would have failed as an allowed failure).
* Silence Minitest for plugin tests.Guo Xiang Tan2014-12-021-0/+1
| | | | | | | | Fixes https://github.com/rails/rails/issues/17340. Use Minitest::BacktraceFilter instead of removing all silencers. This will allow the backtrace for all libraries in the plugin to be shown while removing noise generated by Minitest's backtrace.
* fix test_helper for mountable pluginmasarakki2014-10-131-0/+4
|
* Specify dummy app's db migrate path in plugin's test_helper.rbYukio Mizuta2014-09-161-3/+12
|
* Use dynamic path for dummy app location in plugin's test_helper.rbYukio Mizuta2014-09-141-1/+4
|
* Use default argument when testing generators without the need for extra argsCarlos Antonio da Silva2014-07-301-4/+4
|
* Simplify plugin tests a bit, leave the regexp work for minitestCarlos Antonio da Silva2014-07-301-6/+6
|
* Invert unless..else conditions on JRuby checksCarlos Antonio da Silva2014-07-301-3/+3
|
* Stop requiring mocha automaticallyRafael Mendonça França2014-07-191-0/+1
| | | | | | | | | | | We are planning to remove mocha from our test suite because of performance problems. To make this possible we should stop require mocha on ActionSupport::TestCase. This should not affect applications since users still need to add mocha to Gemfile and this already load mocha. Added FIXME notes to place that still need mocha removal
* Change Gemfile’s double quotes in plugin generatorJosemar Luedke2014-05-101-4/+4
| | | | | Since the generated application’s Gemfile is using single quotation marks, it seems fair to use it on plugin’s Gemfile as well.
* skip-git should not hit git commands plugin generatorsArun Agrawal2014-05-021-8/+18
|
* Works correctly if git not installedRoman Shmatov2014-05-021-0/+24
|
* Update Gemfile templates to provide correct debuggerDavid Rodríguez de Dios2014-04-081-2/+5
|
* Fix build with bundler 1.6Rafael Mendonça França2014-03-261-1/+1
|
* better test error messagesschneems2014-03-141-4/+4
|
* Avoid namespacing routes inside enginesRobin Dupret2014-02-261-0/+12
| | | | | | | | | | | | Since #11544, invoking the controller generator, any generated route is namespaced according to the class_path method. Since a mountable plugin is namespaced, creating a controller inside would generate a namespaced route based on the engine's name. The controller generator now relies on regular_class_path which does not contain the class hierarchy but the given path. Fixes #14079.
* Add missing tests for invalid names in `rails plugin new`Robin Böning2014-01-061-0/+6
| | | | | * Test for: Invalid plugin name, because of reserved rails word. * Test for: Invalid plugin name because of constant name that is already in use.
* Skipping debugger from plugin Gemfile for JRubyArun Agrawal2013-12-061-0/+11
|
* Typo and grammatical fixes [ci skip]Akshay Vishnoi2013-12-021-2/+2
|
* Using activerecord-jdbcsqlite3-adapterArun Agrawal2013-11-231-2/+10
| | | | | PluginGeneratorTest needs to have activerecord-jdbcsqlite3-adapter to pass under JRuby
* s/plugin_new/pluginschneems2013-06-301-0/+350
| | | | | There are historical reasons that the `plugin` command was `plugin_new`, now those are no longer applicable, we should remove the naming edge case from the project. This PR is based off of comments from #11176 ATP Railties
* Remove deprecated plugin generatorGuillermo Iguaran2011-05-241-71/+0
|
* be sure to parenthesize the arguments when the first one is a RegExp literalAkira Matsuda2011-05-181-3/+3
| | | | | | this fixes: "warning: ambiguous first argument; put parentheses or even spaces" because: you need this to tell the parser that you're not calling :/ method (division) details (Japanese!): http://blade.nagaokaut.ac.jp/cgi-bin/vframe.rb/ruby/ruby-dev/42445?42370-43277
* Fix misspelling of 'deprecation' in plugin_generator.Doug Ireton2010-11-161-1/+1
|
* Deprecate plugin generatorPiotr Sarnacki2010-11-161-6/+12
|
* Load generators from both lib/rails/generators and lib/generators. Using the ↵José Valim2010-03-231-1/+1
| | | | former since it's less obstrusive.
* Make plugin generator compatible with new schema.José Valim2010-01-241-1/+1
|
* I removed the rdoc task from plugin RakefileJoshua Peek2010-01-221-1/+1
|
* Get generators tests running on Ruby 1.9.1José Valim2010-01-191-1/+2
|
* Generators load path now will be Ruby load path. If you want to use ↵José Valim2010-01-181-1/+1
| | | | rspec:install generator, you need generators/rspec/install_generator in your load path.
* Plugin generator should use templates.José Valim2010-01-171-0/+15
|
* Move all generators tests to use new test case syntax.José Valim2010-01-031-8/+1
|