[v4.3] Lock solidus_core.gemspec to ransack '< 4.2'#5839
Merged
tvdeyen merged 2 commits intosolidusio:v4.3from Aug 27, 2024
Merged
[v4.3] Lock solidus_core.gemspec to ransack '< 4.2'#5839tvdeyen merged 2 commits intosolidusio:v4.3from
tvdeyen merged 2 commits intosolidusio:v4.3from
Conversation
Failure: /spec/components/solidus_admin/ui/thumbnail/component_spec.rb:6
Error:
/home/circleci/solidus/admin/spec/components/previews/solidus_admin/ui/thumbnail/component_preview/overview.html.erb:53:
numbered parameter is already used in
/home/circleci/solidus/admin/spec/components/previews/solidus_admin/ui/thumbnail/component_preview/overview.html.erb:52:
outer block here Failure/Error: <% image = Spree::Image.new.tap {
_1.define_singleton_method(:attachment) { attachment } } %>
By replaing the second instance of numbered params, we can avoid this
error with no behavioural or functional changes to the code.
Interestingly though, it was only failing on 2 out of our 8 spec runs,
and it did so consistently.
(cherry picked from commit 7176948)
Solidus core's gemspec already required that ransack be '~> 4.0', but the latest version of ransack, v4.2.0, released July 10 2024, introduces a bug. The previous implementation was taking for granted that every predicate would respond to #value, which doesn't seem to be the case when the predicate is an instance of a Arel::SelectManager. This has already been flagged by @spaghetticode in his PR against ransack: activerecord-hackery/ransack#1468 Since there has been little movement on this PR since January, we should lock to a version that works for us since currently many of our product specs are failing. (eg. spec/models/spree/product_spec.rb:659) We can remove this lock once the PR is merged and once the above test (and the others that are failing) are able to pass in ransack v4.2.0 or subsequent versions. (cherry picked from commit 1664d10) # Conflicts: # core/solidus_core.gemspec
tvdeyen
added
backport-v4.3
3 tasks
Member
Author
|
Installer specs will be fixed by solidusio/solidus_starter_frontend#371 |
MadelineCollier
approved these changes
Aug 27, 2024
Contributor
|
This also needs a new backport #6016 |
tvdeyen
added
backport-v4.3
Contributor
Contributor
|
Possibly not! I just collected all PRs that might've been affected by that bug in the GitHub actions config. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Backport
This will backport the following commits from
maintov4.3:Questions ?
Please refer to the Backport tool documentation