aboutsummaryrefslogtreecommitdiffstats
path: root/guides
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | [ci skip] Typo: ActiveSuppport -> ActiveSupportVishal Telangre2019-05-111-3/+3
|/ / / /
* | | | Merge pull request #36241 from ↵Xavier Noria2019-05-111-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | vishaltelangre/fix-confusing-sentence-in-upgrade-guide [ci skip] Fix confusing sentence in upgrade guide
| * | | | [ci skip] Fix confusing sentence in upgrade guideVishal Telangre2019-05-111-1/+1
| | | | |
* | | | | Corrected the sentence in upgrade guideshekhar-patil2019-05-111-1/+1
|/ / / /
* | | | Merge branch 'migration-timestamp-fix'Gannon McGibbon2019-05-101-0/+2
|\ \ \ \ | | | | | | | | | | | | | | | Closes #28707.
| * | | | Add class option timestamps to migration generatorMichael Duchemin2019-02-091-0/+2
| | | | | | | | | | | | | | | | | | | | Fixes GH#28706. Now rails g migration create_users and rails g model User have the same behavior for timestamps since they implement the same migration template. The expected behavior is that this create table migration will create the table with timestamps unless you pass --no-timestamps or --skip-timestamps to the generator. The expected migration should match what you get when you use the model generator. Using the migration generator, which doesn't have a class_option for timestamps would cause them to not be added to the migration file. Now the migration behavior of the migration generator, create_table only, is aligned with the migration behavior of the model generator. Also modified relevant example of ActiveRecord Migrations Guide.
* | | | | Merge pull request #36184 from vishaltelangre/as-monotonic-timed-subscriberEileen M. Uchitelle2019-05-101-1/+10
|\ \ \ \ \ | | | | | | | | | | | | Introduce ActiveSupport::Notifications.monotonic_subscribe
| * | | | | Introduce ↵Vishal Telangre2019-05-101-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 'ActiveSupport::Notifications::Fanout::Subscribers::MonotonicTimed' and 'ActiveSupport::Notifications::monotonic_subscribe' Also, change the signature of ‘ActiveSupport::Notifications::Fanout#subscribe’ to accept optional ‘monotonic’ boolean argument. Then initialize either a ‘Timed’ or ‘MonotonicTimed’ subscriber based on the value of ‘monotonic’ parameter. Introduce ‘ActiveSupport::Notifications::monotonic_subscribe’ method Also, provision ‘ActiveSupport::Notifications::subscribed’ to optionally accept ‘monotonic’ boolean argument. Update documentation for ActiveSupport::Notifications Add tests Update guides documentation under the 'Active Support Instrumentation' chapter Incorporate feedback: use optional keyword argument to specify optional 'monotonic' option to 'subscribed' method Fix a typo
* | | | | | fixes configuration examples [ci skip]Xavier Noria2019-05-091-3/+3
|/ / / / /
* | | | | documents restriction for explicit namespaces [ci skip]Xavier Noria2019-05-081-0/+34
| | | | |
* | | | | documents how to use the classic autoloader in Rails 6 [ci skip]Xavier Noria2019-05-081-0/+11
| | | | |
* | | | | Update testing guide to reflect changes from #36047Richard Macklin2019-05-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In #36047 we moved `take_failed_screenshot` from an `after_teardown` hook to a `before_teardown` hook. However, I didn't realize the Testing rails guide was explicitly mentioning that it happened inside `after_teardown`. So this updates the docs to be consistent with that change. [ci skip]
* | | | | documents autoloading in the upgrading guide [ci skip]Xavier Noria2019-05-081-0/+172
| | | | |
* | | | | Merge pull request #36203 from st0012/fix-command-in-contributing-guideRyuta Kamizono2019-05-081-1/+1
|\ \ \ \ \ | | | | | | | | | | | | Update directory name in example commands [ci skip]
| * | | | | Update directory name in sample commandsst00122019-05-081-1/+1
| | | | | |
* | | | | | Typo in the release noteAkira Matsuda2019-05-081-1/+1
|/ / / / / | | | | | | | | | | | | | | | [ci skip]
* | | / / Fixed typo of dot position [skip ci]soartec-lab2019-05-071-1/+1
| |_|/ / |/| | |
* | | | [ci skip] Correct the stylesheet name used in the guide.Alec Clarke2019-05-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the Action Text guides, `app/assets/stylesheets/actiontext.css` is specified as the file used to style the Action Text editor and content but the actual file generated from `rails action_text:install` is `app/assets/stylesheets/actiontext.scss`. This change simply corrects the file extension shown in the guide.
* | | | Add Action Cable Release Notes [ci skip]Alex Kitchens2019-05-021-11/+30
| | | | | | | | | | | | | | | | Co-Authored-By: प्रथमेश Sonpatki <csonpatki@gmail.com>
* | | | Update guides/source/6_0_release_notes.mdConnor Shea2019-05-021-1/+1
| | | | | | | | | | | | Co-Authored-By: prathamesh-sonpatki <csonpatki@gmail.com>
* | | | Added release notes for Active Support [ci skip]Prathamesh Sonpatki2019-05-021-0/+186
| |/ / |/| |
* | | Update asset compression text [ci skip]Sharang Dashputre2019-05-021-1/+1
| | |
* | | Merge pull request #36149 from alexcameron89/add_active_storage_rnRafael França2019-05-011-2/+60
|\ \ \ | | | | | | | | Add Release Notes for Active Storage
| * | | Add Release Notes for Active Storage [ci skip]Alex Kitchens2019-05-011-2/+60
| | | | | | | | | | | | | | | | Co-authored-by: Abhay Nikam <nikam.abhay1@gmail.com>
* | | | Merge pull request #36155 from prathamesh-sonpatki/am-release-notesRafael França2019-05-011-0/+24
|\ \ \ \ | | | | | | | | | | Active Model release notes [ci skip]
| * | | | Active Model release notes [ci skip]Prathamesh Sonpatki2019-05-011-0/+24
| |/ / /
* | | | Merge pull request #36157 from prathamesh-sonpatki/getting-started-updatesRafael França2019-05-011-5/+3
|\ \ \ \ | | | | | | | | | | Updates to getting started per Rails 6.0 changes [ci skip]
| * | | | Updates to getting started per Rails 6.0 changes [ci skip]Prathamesh Sonpatki2019-05-011-5/+3
| |/ / /
* / / / Remove dynamic_form gem references in guidesCarles Jove i Buxeda2019-04-301-21/+0
|/ / / | | | | | | | | | This gem has not been updated since April 2014 and 2 of the 4 methods it introduces have been broken since Rails 4
* | | Action Mailer release notes [ci skip]Prathamesh Sonpatki2019-04-301-0/+33
| | |
* | | Merge pull request #36130 from alexcameron89/add_action_view_rnप्रथमेश Sonpatki2019-04-301-0/+53
|\ \ \ | | | | | | | | [ci skip] Add 6.0 Release Notes for Action View
| * | | [ci skip] Add 6.0 Release Notes for Action ViewAlex Kitchens2019-04-291-0/+53
| | | | | | | | | | | | | | | | I've added release notes based off of the CHANGELOG for Action View.
* | | | Fix incorrect url in guide [ci skip]Robin Fisher2019-04-291-1/+1
|/ / / | | | | | | The example functional test lists the 'create' route as article_url rather than articles_url
* | | fixes typo in guide [ci skip]Xavier Noria2019-04-281-1/+1
| | |
* | | new config to opt-out from adding app directories to $LOAD_PATHXavier Noria2019-04-281-0/+2
| | |
* | | [ci skip] Update the guide's model generator output.Alec Clarke2019-04-271-4/+7
| | | | | | | | | | | | | | | | | | | | | The model generator code sample used in the command line guides was displaying an outdated output for the generator's usage. This change updates the sample to mirror what's currently output when running `$rails generate model`.
* | | [ci skip] Add 6.0 Release Notes for Action PackAlex Kitchens2019-04-261-0/+68
| | | | | | | | | | | | | | | | | | I've gone through the CHANGELOG for Action Pack, pulled out anything that was backported, rephrased some of the descriptions and found their PR's/commits as links.
* | | [ci skip] Get npm just the way they like itKasper Timm Hansen2019-04-251-1/+1
| | |
* | | [ci skip] Remove à la just like that.Kasper Timm Hansen2019-04-251-1/+2
| | |
* | | [ci skip] Documentation pass of upgrading guide.Kasper Timm Hansen2019-04-251-14/+14
| | |
* | | Update bug report templatesRyuta Kamizono2019-04-255-8/+8
| | | | | | | | | | | | Bump gem version to 6.0.0.rc1.
* | | Adds documentation for has_one touch option after #35869 [ci skip]Abhay Nikam2019-04-251-2/+25
| | |
* | | Merge pull request #32313 from lulalala/model_error_as_objectRafael França2019-04-241-6/+6
|\ \ \ | | | | | | | | Model error as object
| * | | Raise deprecation for calling `[:f] = 'b'` or `[:f] << 'b'`lulalala2019-03-311-6/+6
| | | | | | | | | | | | | | | | Revert some tests to ensure back compatibility
* | | | Start Rails 6.1 developmentRafael Mendonça França2019-04-241-33/+1
| |_|/ |/| |
* | | Merge pull request #36066 from st0012/update-controller-cache-docRafael França2019-04-231-2/+2
|\ \ \ | | | | | | | | Update document about perform_caching's default value [ci skip]
| * | | Update document about perform_caching's default valuest00122019-04-241-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Clarify that both `config.action_controller.perform_caching` and `config.action_mailer.perform_caching`'s default are `true`. This default is set in `AbstractController::Caching`. One can verify this by commenting out all ``` @controller.perform_caching = true ``` in `actionpack/test/controller/caching_test.rb` and run the tests. They should still pass.
* | | | Make docs on form_with_generates_ids config option match the valueDavid Shaffer2019-04-231-1/+1
|/ / / | | | | | | | | | [skip ci]
* | | Merge pull request #36063 from ↵Rafael França2019-04-231-8/+0
|\ \ \ | | | | | | | | | | | | | | | | albertoalmagro/finish-documentation-for-after-save-commit Remove reminiscences from previous documentation
| * | | Remove reminiscences from previous documentation [ci skip]Alberto Almagro2019-04-231-8/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In #35861 documentation for `after_save_commit` was added, but also old documentation was adapted. I think adapting the old documentation is not necessary because there are already examples for `after_commit` on `:destroy` above. On top of that the action invoked by the callback on `:destroy` (`:log_user_saved_to_db`) talks about saving when the object is destroyed, which can be misleading. As I believe the documentation added by #35861 is already enough this patch removes the modified part, which made sense before adding docs for `after_save_commit` but is already covered by other parts of this guide.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 02:09:13 +0000