Join GitHub today
Merge Arel #32097
We've been bumping Arel in lockstep with AR for some time now: every Rails release requires a new Arel release, and Arel releases occur specifically for Rails releases.
We're not gaining any maintenance freedom by keeping it as a separate gem, while we are paying the costs of coordination.
Scrolling through https://rubygems.org/gems/arel/reverse_dependencies shows few notable downstreams that aren't also depending on Active Record, so this change doesn't force new dependencies onto the ecosystem at large. We'll release a new version of the
We have no plans to rename the top level
This commit will help me a lot because when some
As a 3rd party database adapter maintainer, I'd like to know if if there is a plan to separate visitors for non bundled database adapters, such as
Actually, I'd like Arel will have these visitors at least for Rails 6, Just wanted to prepare if there is a plan.
@yahonda in the short term, we'll keep the visitors in place, despite the inconsistency.
Looking forward, I'd like to rebalance some responsibilities between the Arel and AR parts, and at that time I expect we'll try to move them closer together. But no concrete plans for now.