eileencodes 656c6faf78 Allow applications to change the behavior for a strict loading violation ... Originally strict loading violations would always raise an error if turned on for an association. This change allows for an application to optionally log instead of raise. The behavior here is similar to how strong parameters work. By default all environments will raise. An application may want to use log in production while working on finding all lazily loaded associations. Set `config.active_record.action_on_strict_loading_violation` to `:log` in your application to log instead of raise.		2020-11-02 13:01:50 -05:00
..
assets	Fix triple-click-to-select for IRB code examples [ci-skip]	2020-10-31 16:47:52 -05:00
bug_report_templates	Add Action Mailbox bug report templates	2020-07-15 11:04:12 -04:00
rails_guides	Fix copy button for IRB code examples [ci-skip]	2020-10-31 16:57:17 -05:00
source	Allow applications to change the behavior for a strict loading violation	2020-11-02 13:01:50 -05:00
.document
CHANGELOG.md	Fallback to $MEMCACHE_SERVERS if no servers given	2020-10-20 23:50:52 -04:00
rails_guides.rb	Use safe nav operator when calling RailsGuides::Generator.new	2018-12-05 12:41:07 +09:00
Rakefile	Remove references to WARNINGS environment variable [ci skip]	2020-07-05 16:40:52 +01:00
w3c_validator.rb	Use frozen string literal in guides/	2017-08-13 22:04:09 +09:00