Allow Rails 7.2 #5843

We introduced a custom Ransacker to allow filtering producs by their variants option values in the new admin interface. This ransacker is broken in latest Ransack v4.2 and overly complicated. By introducing a option_values association to products, that does the same join over variants_including_master and their distinct option_values we can use normal ransack search. Quoting the Ransack documentation: > "Ransackers, like scopes, are not a cure-all. Many use cases can be better solved with a standard Ransack search on a dedicated database search field, which is faster, index-able, and scales better than converting/ransacking data on the fly."

Now that we removed the broken ransacker in previous commit, we can allow Ransack v4.2 - with Rails 7.2 support - again.

We do not use the custom ransacker this was necessary for

We need at least v3.7 of awesome_nested_set for Rails 7.2 support

Rails 7.2 requires it and 3.0 is out of support anyway.

Rails 7.2 removed migration_context from ActiveRecord::Base.connection

The file lives in tasks and the projects are in the root folder.

Without that ActiveRecord 7.2 expects a DB table for it.

Now, with Ruby 3.1 we need to address some code style

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Allow Rails 7.2 #5843

Allow Rails 7.2 #5843

Commits on Sep 12, 2024

Allow Rails 7.2 #5843

Are you sure you want to change the base?

Allow Rails 7.2 #5843

Commits on Sep 12, 2024