Sean

As this is a large change, and because of https://github.com/activerecord-hackery/ransack/issues/1644, moving the unreleased code to the v5.0.0 branch. To test against this release as it unflolds, please point your Gemfile...

@deivid-rodriguez @gregmolnar if either of you have time, I can send you the PRs for this effort

@gregmolnar thanks for your comments, my laptop is actually in the shop being repaired right now. I should have it back in few days and will reply in more detail...

> it would be beneficial to look into moving away from relying on Active Record's private APIs. It would make ransack way more stable and we wouldn't need to deal...

Related https://github.com/rgeo/activerecord-postgis-adapter/issues/183#issuecomment-225871427

Great, thank you for explaining that @tindron I think it would be best to look at how the dependency can be removed at some point. If a way can be...

@tindron see also https://github.com/activerecord-hackery/ransack/issues/1639 If you have any thoughts on this, please let me know.

Reopening due to https://github.com/activerecord-hackery/ransack/issues/1644 and https://github.com/activerecord-hackery/ransack/pull/1645 Adding to v5.0.0 planning

Hi @rocket-turtle thanks for the heads up. Polyamorous was officially [retired back in 2019](https://github.com/activerecord-hackery/polyamorous), I had always planned to remove it completely from Ransack. I think there are 2 options...

Good luck with it @rocket-turtle I wasn't directly involved in that change, but I think it is because there is no Rails 7.3 - it went directly from 7.2.x to...