fix(active_record): ArgumentError in AssociationRelation #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fix is specifically for
AssociationRelation
, which is the class that you get when you chain awhere
onto an association and then try to use methods such asfirst_or_initialize
on the result.In Rails 6, the signature of
build
,create
, andcreate!
changed. They no longer accept*args
. See rails/rails@f1c1c43 for more details on that change.When this gem's patch on
first_or_initialize
delegates tocreate
, for example, it tries to passoptions
as a second parameter. This succeeded with the previous signature of these methods, but in Rails 6, this fails as the methods no longer accept a second argument.This commit adds another patch to
AssociationRelation
to override these methods so that they accept theoptions
argument and pass it on.Fixes #19