Julian Nadeau 901d62c586 Only assign @new_record_before_save once in autosave_association ... If we defined a callback before an association that updates the object, then this may end up being manipulated to being `false` when it should be `true`. We guard this be only defining it once. The implication of it being false, in this case, is that the children aren't updated with the parent_id and so they fail to associate to one another. See https://github.com/rails/rails/issues/38120 for more details		2020-01-06 12:57:33 -05:00
..
assets	Highlight code with Prism on 'turbolinks:load' [ci skip]	2019-12-17 19:38:07 -05:00
bug_report_templates	Style	2019-12-04 21:10:58 -05:00
rails_guides	Add missing languages for guides code blocks [ci skip]	2019-12-17 19:38:45 -05:00
source	Only assign @new_record_before_save once in autosave_association	2020-01-06 12:57:33 -05:00
.document
CHANGELOG.md	Start Rails 6.1 development	2019-04-24 15:57:14 -04:00
rails_guides.rb	Use safe nav operator when calling RailsGuides::Generator.new	2018-12-05 12:41:07 +09:00
Rakefile	Respect ENV variables when finding DBs etc for the test suite	2019-02-06 01:20:06 +10:30
w3c_validator.rb	Use frozen string literal in guides/	2017-08-13 22:04:09 +09:00