aboutsummaryrefslogtreecommitdiffstats
path: root/railties
Commit message (Collapse)AuthorAgeFilesLines
...
* | Only mount the ActionCable server if ApplicationCable has been definedDavid Heinemeier Hansson2015-12-161-1/+1
| |
* | By default, mount Action Cable on the routerDavid Heinemeier Hansson2015-12-161-0/+3
| |
* | Add default redis config for Action CableDavid Heinemeier Hansson2015-12-162-0/+9
| |
* | Merge branch 'master' into merge-action-cableRafael Mendonça França2015-12-1620-69/+102
|\ \
| * | Use sprockets 3 in the Rails 5 releaseRafael Mendonça França2015-12-163-8/+7
| | |
| * | Merge pull request #22567 from gsamokovarov/introduce-application-recordRafael França2015-12-167-1/+29
| |\ \ | | | | | | | | Introduce ApplicationRecord, an Active Record layer supertype
| | * | Introduce ApplicationRecord, an Active Record layer supertypeGenadi Samokovarov2015-12-167-1/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's pretty common for folks to monkey patch `ActiveRecord::Base` to work around an issue or introduce extra functionality. Instead of shoving even more stuff in `ActiveRecord::Base`, `ApplicationRecord` can hold all those custom work the apps may need. Now, we don't wanna encourage all of the application models to inherit from `ActiveRecord::Base`, but we can encourage all the models that do, to inherit from `ApplicationRecord`. Newly generated applications have `app/models/application_record.rb` present by default. The model generators are smart enough to recognize that newly generated models have to inherit from `ApplicationRecord`, but only if it's present.
| * | | Run railties generated app tests in test enveileencodes2015-12-151-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Running railties generated app tests in development env can cause unintended consequences. The environments are different and tests aren't meant to be run in development mode. The changes to the generator exposed this issue where the random test order in the generated apps could cause problems when those tests are run in development mode. Particularly we saw failures in `railties/test/application/rake_test.rb` generated apps that used the scaffold to create applications and then run the migration and immediately run the tests. The error we saw was `ActiveRecord::RecordNotFound: Couldn't find User with 'id'=980190962` and seemed to only occur if the destroy test ran first. I'm not entirely sure _why_ this causes that error to be thrown but I believe it is related to the environments being different.
| * | | Update test generators to use ActionDispatch::IntegrationTestAbdelkader Boudih2015-12-158-49/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In Rails 5.1 `ActionController::TestCase` will be moved out of Rails into it's own gem. Please use `ActionDispatch::IntegrationTest` going forward. This changes the generators to use `ActionDispatch::IntegrationTest` and the required URL setup (rather than symbols) for each of the controller actions. Updated fix to #22076.
| * | | Do not default to any SerializerSantiago Pastorino2015-12-153-8/+2
| |/ / | | | | | | | | | We will wait until 5.1 to make a decision
* | | Only include action cable meta tags if it is not skippedRafael Mendonça França2015-12-161-0/+2
| | |
* | | Needless whitespaceDavid Heinemeier Hansson2015-12-161-2/+0
| | |
* | | Include the action cable URL meta tag by defaultDavid Heinemeier Hansson2015-12-161-1/+3
| | |
* | | Assume that the cable server is running in-process by default, offer option ↵David Heinemeier Hansson2015-12-161-0/+3
| | | | | | | | | | | | to change that in config/environments/production.rb
* | | Fix the engine referenceRafael Mendonça França2015-12-161-1/+1
| | |
* | | Doh, should have read ff370ee61754b00f864f3ddd0af62be4dfa0de67David Heinemeier Hansson2015-12-161-1/+1
| | | | | | | | | | | | Indeed we need this to be an engine for the internal assets to work
* | | Another bad reference to engine instead of railtieDavid Heinemeier Hansson2015-12-161-1/+1
| | |
* | | We are using railtie, not engineDavid Heinemeier Hansson2015-12-161-1/+1
| | |
* | | Accept a Pathname in Application#config_forRafael Mendonça França2015-12-152-1/+20
| | | | | | | | | | | | That would make possible to use it with action cable configuration.
* | | Merge remote-tracking branch 'origin/master' into merge-action-cableRafael Mendonça França2015-12-158-31/+31
|\| |
| * | Internal test migrations use the private 'Current' versionMatthew Draper2015-12-154-15/+15
| | | | | | | | | | | | | | | | | | | | | | | | Apart from specific versioning support, our tests should focus on the behaviour of whatever version they're accompanying, regardless of when they were written. Application code should *not* do this.
| * | Ensure generated migrations include a version numberMatthew Draper2015-12-153-14/+14
| | |
| * | Update seeds.rb.ttPaul Clegg2015-12-141-2/+2
| | | | | | | | | | | | Rahm Emanuel doesn't deserve to be in Rails.
* | | Action Cable need to be a engineRafael Mendonça França2015-12-151-1/+1
| | | | | | | | | | | | Otherwise assets will not work
* | | Switch from engine to railtieDavid Heinemeier Hansson2015-12-151-1/+1
| | |
* | | Add option to skip Action CableRafael Mendonça França2015-12-143-2/+10
| | |
* | | Add action_cable to rails/all and application.rbRafael Mendonça França2015-12-142-9/+11
|/ /
* | Revert "Merge pull request #22569 from seuros/remove-test-case"eileencodes2015-12-139-31/+30
| | | | | | | | | | | | | | | | | | This reverts commit 9712a7a12b7f9e4dcef751ceda8a73c3f4beb11f, reversing changes made to 3e65c3d3886336e9145438cdeacaf4ebec6a48b8. Reverting because this caused test failures and while we have a followup branch there is still one failure that happens randomly and isn't straight forward to fix.
* | Merge pull request #22569 from seuros/remove-test-caseEileen M. Uchitelle2015-12-139-30/+31
|\ \ | | | | | | Controller generators should be creating IntegrationTest stubs instea…
| * | Controller generators should be creating IntegrationTest stubs instead of ↵Abdelkader Boudih2015-12-139-30/+31
| | | | | | | | | | | | ControllerTest
* | | Merge branch 'rails-rake-proxy'Kasper Timm Hansen2015-12-133-6/+56
|\ \ \
| * | | Implement Rake proxy for Rails' command line interface.Dharam Gollapudi2015-12-133-1/+57
|/ / / | | | | | | | | | | | | | | | | | | Allows any Rake task to be run through `bin/rails` such as `bin/rails db:migrate`, `bin/rails notes` etc. The Rake tasks are appended to Rails' help output, and blend in as standard commands.
* | | Merge pull request #22574 from gsamokovarov/scaffold-500Kasper Timm Hansen2015-12-133-3/+3
|\ \ \ | | | | | | | | Prevent a 500 in the default controller scaffold
| * | | Prevent a 500 in the default controller scaffoldGenadi Samokovarov2015-12-133-3/+3
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you update a record with no attributes, you'll hit a 500 from a guard in `assign_attributes` raising: ```ruby ArgumentError: When assigning attributes, you must pass a hash as an argument. app/controllers/users_controller.rb:44:in `block in update' app/controllers/users_controller.rb:43:in `update' test/controllers/users_controller_test.rb:37:in `block in <class:UsersControllerTest>' ``` Not a biggie, but may be quite confusing for the folks new to the framework.
* | | Merge pull request #22573 from gsamokovarov/web-console-3-0Kasper Timm Hansen2015-12-132-3/+3
|\ \ \ | | | | | | | | Update web-console to 3.0.0
| * | | Update web-console to 3.0.0Genadi Samokovarov2015-12-132-3/+3
| |/ / | | | | | | | | | | | | Web Console 3.0.0 is compatible with Rails 5, while the 2.x.x releases aren't.
* | | Nodoc Rails command.Kasper Timm Hansen2015-12-131-1/+1
| | | | | | | | | | | | | | | | | | | | | The API isn't ready yet, which means we haven't documented it. People can't make their own commands, so there's no reason to show it in generated documentation.
* | | let config.file_watcher be the way to enable the evented file watcherXavier Noria2015-12-134-26/+21
|/ / | | | | | | | | | | | | | | | | | | | | Before this commit, the sole presence of the Listen constant enabled the evented file watcher (unless listen resorted to the polling backend). This way, applications may depend on listen for other stuff independently of this feature. Also, allows teams with mixed setups to decide at boot time whether the evented watcher should be enabled for each particular instance.
* | show relative path the rerun snippet of test runner in rails engineyuuji.yaginuma2015-12-104-23/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | Since the absolute path is not required to re-run the test, modified so that unnecessary information is not displayed. ```ruby # before bin/rails test /path/to/blorgh/test/integration/navigation_test.rb:5 # after bin/rails test test/integration/navigation_test.rb:5 ```
* | Fixed typo in mysql client parameterKent Sibilev2015-12-091-1/+1
| |
* | Remove duplicated assertion from api_app_generator testsJorge Bejar2015-12-091-2/+0
| |
* | We don't need to set config.debug_exception_response_format given that :api ↵Jorge Bejar2015-12-092-10/+0
| | | | | | | | is the default value for only API apps
* | Make debug_exception_response_format config depends on api_only when is not setJorge Bejar2015-12-092-2/+37
| |
* | Add tests for api_only configuration settingJorge Bejar2015-12-091-0/+15
| |
* | Adjust comment in development.rb template file for app generatorJorge Bejar2015-12-091-3/+0
| |
* | Update Changelog with the added response_format option in AD::DebugExceptionsJorge Bejar2015-12-091-0/+9
| |
* | debug_exception_response_format needs to be writeable in ConfigurationJorge Bejar2015-12-091-2/+2
| |
* | Fix indent in generated Rails API env fileJorge Bejar2015-12-091-6/+6
| |
* | DebugException initialize with a response_format valueJorge Bejar2015-12-091-1/+1
| |
* | Add debug_exception_response_format config to configure DebugExceptionJorge Bejar2015-12-093-30/+43
| | | | | | | | behavior