aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/generators/app_generator_test.rb
Commit message (Collapse)AuthorAgeFilesLines
* do not run `git init` when specify the `pretend` optionyuuji.yaginuma2017-01-231-0/+1
| | | | | When specifying the `pretend` option, expect that no processing will be done, so do not execute `git init` as well.
* Initalize git repo when creatin new rails appdixpac2017-01-121-2/+7
| | | | | * If `--skip-git` is not specified initalize git repo when creating new rails app
* Revert "Merge pull request #27619 from dixpac/add_missing_generator_test"yuuji.yaginuma2017-01-101-5/+0
| | | | | | | | | | This reverts commit 8cb3cdffdb70f3575518d24ea96ec891e40d21d0, reversing changes made to 3bc747bd8676dc940b531067e2861dcd4ac28efc. Reason: This test already exists in `SharedGeneratorTests`. Ref: https://github.com/rails/rails/blob/master/railties/test/generators/shared_generator_tests.rb#L109..L112 https://github.com/rails/rails/blob/master/railties/test/generators/app_generator_test.rb#L55..L56
* Test `--skip-git` generator optiondixpac2017-01-091-0/+5
|
* Remove bin/yarn if yarn is skipped, tidy up testsPrathamesh Sonpatki2017-01-011-0/+7
| | | | | | - No need to remove bin/yarn separately for API only apps because :skip_yarn is set to true for API only apps. - Added a test for :skip_yarn config.
* Privatize unneededly protected methods in Railties testsAkira Matsuda2016-12-241-1/+1
|
* fix broken tests (#27308)Yuji Yaginuma2016-12-081-3/+2
| | | Follow up to 0d20530e5edfd7d00fbc2a38ef5f87eca6ccc924
* Make Yarn the default, drop default vendor/asset directories (#27300)David Heinemeier Hansson2016-12-081-24/+11
|
* Yarn: Move node_modules, package.json, and yarn.lock file to vendor (#27245)David Heinemeier Hansson2016-12-011-1/+1
| | | Move node_modules, package.json, and yarn.lock file to vendor
* Merge pull request #26836 from Liceth/npmGuillermo Iguaran2016-11-291-0/+24
|\ | | | | Add Yarn support in new apps using --yarn option
| * Add node_modules path to assets load paths when --yarn option is usedLiceth Ovalles2016-11-281-0/+1
| |
| * Add package.json for Yarn if --yarn option is addedLiceth Ovalles2016-11-281-0/+23
| |
* | rails-ujs is now shipped with Action ViewGuillermo Iguaran2016-11-291-2/+0
|/
* Don't add jQuery by default in new apps and use rails-ujs as UJS adapter insteadGuillermo Iguaran2016-11-211-12/+8
|
* Add test for #25248Sean Griffin2016-11-121-0/+10
|
* Don't put db:migrate and db:setup in binfiles if activerecord is excludedBouke van der Bijl2016-11-011-0/+6
|
* remove assets config from `new_framework_defaults` if `--skip-sprockets` is trueyuuji.yaginuma2016-10-251-0/+3
| | | | If `sprockets` is not loaded, `Rails.application.config.assets` is not defined.
* don't create db directory when skip active_recordJosé Gomes Júnior2016-10-211-0/+1
|
* Fix test for the edge generatorRafael Mendonça França2016-09-141-1/+1
|
* Merge pull request #26157 from ↵Rafael França2016-08-161-0/+1
|\ | | | | | | | | y-yagi/remove_test_mailers_when_skipping_action-mailer remove "test/mailers" directory when skipping action-mailer
| * remove "test/mailers" directory when skipping action-maileryuuji.yaginuma2016-08-141-0/+1
| | | | | | | | Related to #26146
* | Add three new rubocop rulesRafael Mendonça França2016-08-161-1/+1
|/ | | | | | | | Style/SpaceBeforeBlockBraces Style/SpaceInsideBlockBraces Style/SpaceInsideHashLiteralBraces Fix all violations in the repository.
* Ensure app/mailers is removed when skipping action-mailerBrian Cardarella2016-08-121-0/+1
| | | | Closes #26145
* normalizes indentation and whitespace across the projectXavier Noria2016-08-061-1/+1
|
* applies new string literal convention in railties/testXavier Noria2016-08-061-49/+49
| | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
* A generated app should not include Uglifier with `--skip-javascript` option.Ben Pickles2016-07-261-0/+5
|
* Enforce minimal web-console version for Rails 5Genadi Samokovarov2016-07-211-2/+2
| | | | | | | | | | | | | | | I dropped the version constraint in web-console with the idea it will be easier to upgrade the console between Rails releases. However, issues like #25899 started popping up. I'm reintroducing the constraint, but this time, I don't set an upper limit to the major version. This will keep the web-console in a version that always works for the current Rails version and can be easily upgraded to the last one with `bundle update`. We may need to backport this for Rails 5.0.1. Fixes #25899.
* Setup default session store internally, no longer through an application ↵Prathamesh Sonpatki2016-07-171-10/+0
| | | | | | | | | | | | | initializer - By default the session store will be set to cookie store with application name as session key. - Older apps are not affected as they will have the session store initializer generated by Rails in older versions, and Rails will not overwrite the session store if it is already set or disabled. - But new apps will not have the initializer, instead the session store will be set to cookie store by default. - Based on comment by DHH here - https://github.com/rails/rails/issues/25181#issuecomment-222312764.
* Do not run `bundle install` when generating a new plugin.Rafael Mendonça França2016-07-011-26/+61
| | | | | | Since bundler 1.12.0, the gemspec is validated so the `bundle install` command will fail just after the gem is created causing confusion to the users. This change was a bug fix to correctly validate gemspecs.
* Remove FORCE option as it was only needed for testsPrathamesh Sonpatki2016-06-071-1/+3
| | | | - Adjusted tests instead.
* Fix minor regression about old apps not getting per_form_csrf and ↵Prathamesh Sonpatki2016-06-041-17/+6
| | | | | | | | | | | | request_forgery_protection configs - Earlier per_form_csrf_tokens and request_forgery_protection config files were generated for old apps upgraded to Rails 5. - But when we collapsed all initializers into one file, the entire file does not get created for old apps. - This commit fixes it and also changes values for all new defaults for old apps so that they will not break. - Also added a test for `rails app:update`.
* Collapse all new default initializers into a single filePrathamesh Sonpatki2016-05-311-91/+10
| | | | | | - Adjusted tests also for this new behavior. - Based on the discussion in https://github.com/rails/rails/pull/25184#issuecomment-222454583.
* Move new default initializers into separate directoryPrathamesh Sonpatki2016-05-281-17/+17
| | | | | | - These initializers are new defaults for Rails 5 and newly generated apps do not need to change them. - Fixes #25181
* Add compatibility for Ruby 2.4 `to_time` changesAndrew White2016-04-231-0/+28
| | | | | | | | | | | | | | | In Ruby 2.4 the `to_time` method for both `DateTime` and `Time` will preserve the timezone of the receiver when converting to an instance of `Time`. Since Rails 5.0 will support Ruby 2.2, 2.3 and later we need to introduce a compatibility layer so that apps that upgrade do not break. New apps will have a config initializer file that defaults to match the new Ruby 2.4 behavior going forward. For information about the changes to Ruby see: https://bugs.ruby-lang.org/issues/12189 https://bugs.ruby-lang.org/issues/12271 Fixes #24617.
* Use new hash syntax (#24464)Jeroen Visser2016-04-081-2/+2
| | | | | | * Updated syntax * Updated tests to match syntax
* Add tests for file_watcher config on updateArthur Neves2016-03-211-0/+14
| | | | [related #24243]
* Merge pull request #23940 from prathamesh-sonpatki/rm-with-dispatchersRafael França2016-03-091-12/+12
|\ | | | | Remove passing `with_dispatchers` to AppGenerator
| * Remove passing `with_dispatchers` to AppGeneratorPrathamesh Sonpatki2016-03-091-12/+12
| | | | | | | | | | | | | | - While working on https://github.com/rails/rails/pull/22790 I found out that we pass `with_dispatchers: true` but it's not used at all by Rails. - We were passing `with_dispatchers: true` in few tests too but again it's not used by Rails.
* | Fix the tests after e594000Genadi Samokovarov2016-03-081-2/+2
| |
* | Drop the explicit version requirements for web-consoleGenadi Samokovarov2016-03-081-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Between major versions 2 and 3, we hit a bug. It's fixed in version 3, however, the explicit 2.x requirement of `~> '2.0'` will prevent people from getting the fix with `bundle update` and they would have to explicitly set the constraint to `~> '3.0'`. For more information see: rails/web-console#178. I propose we drop the explicit version constraints in the Gemfile. Web Console has been relatively stable for the past couple of years, and I don't anticipate any major alterations, like we saw between major versions 1 and 2.
* | Merge pull request #24001 from 5t111111/fix-gsub-cookies_serializerRafael França2016-03-021-1/+2
|\ \ | | | | | | Fix description in cookies_serializer.rb being corrupted by gsub when updating
| * | Fix description in cookies_serializer.rb being corrupted when updatingHirofumi Wakasugi2016-03-021-1/+2
| | |
* | | Fix typo in app_generator_test.rbHirofumi Wakasugi2016-03-021-1/+1
|/ /
* | Merge pull request #23935 from y-yagi/convert_cable_coffee_to_javascriptRafael França2016-03-011-1/+1
|\ \ | | | | | | convert cable.coffee to cable.js
| * | convert cable.coffee to cable.jsyuuji.yaginuma2016-02-281-1/+1
| |/ | | | | | | In order to eliminate the dependecy of CoffeeScript.
* | Mock fork twiceRafael Mendonça França2016-03-011-1/+1
| |
* | generate config/spring.rb in new applications [closes #18874]Xavier Noria2016-02-291-0/+2
|/
* remove rack cors initializer when updatingyuuji.yaginuma2016-02-271-0/+26
| | | | Rack cors initializer is only necessary to API-only applications, for when the update is unnecessary.
* [close #23681] Use puma 3.0.0+ schneems2016-02-261-0/+5
| | | | | Puma 3.0 and up introduced compatibility to read from `config/puma.rb` when booting from the command `$ rails server`https://github.com/puma/puma/pull/856.
* Old applications will not get the ssl_options initializerPrathamesh Sonpatki2016-02-251-0/+28
| | | | | - We will remove the initializer for old apps which are migrated to Rails 5 so that they are not affected by this breaking change.