🐞 Bug Report: Conflict between `active_record_extended` and Rails 7.2+ `with_recursive`

[Antoine-Gerard]

Summary:

When using ActiveRecord.with_recursive, an error is raised due to a conflict with ActiveRecordExtended’s monkey patch that defines method with_values= .

Error Message

undefined` method `with_values=' for nil:NilClass (NoMethodError) 

Cause:
The gem active_record_extended defines a monkey patch that introduces a with_values= method, which collides with internal behavior of ActiveRecord’s CTE implementation in Rails 7.2+.

This leads to with_values= being called on nil instead of a valid relation or CTE builder, because the method name overlaps with internal expectations.

Steps to reproduce:

1. Use Rails 7.2.1+ with ActiveRecord.with_recursive.
2. Have active_record_extended in your Gemfile.
3. Try using .with_recursive(...) on any model.
4. Observe the crash on with_values=.

Expected behavior:

ActiveRecord’s with_recursive should work normally when the gem is present.

Actual behavior:

NoMethodError is raised due to an unexpected override of with_values=.

[GeorgeKaraszi]

Hey @Antoine-Gerard I'm aware of the problems. I plan to set aside some time in the near future to explore the depreciation of CTE support. Over the years, the Rails team has brought to the forefront first-class CTE support, making my implementation somewhat obsolete.