[WIP] modifier "or" not work correct #1609
Draft
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.
Search#build
andGrouping#build
Summary
Issue Fixed: ✅
The reported issue where
ransack(m: 'or', id_eq: "12", name_contains: "12").result
generated an AND query instead of an OR query has been resolved.Root Cause Identified:
The
Search#build
method was not properly handling the top-levelm
parameter. While the documentation indicated this should work, the existing logic had a gap in processing the combinator parameter at the top level (as opposed to within sub-groupings).Minimal Fix Implemented:
Key Benefits:
Tests Added:
Expected User Impact:
Users can now use
ransack(m: 'or', field1: value1, field2: value2)
at the top level and get OR queries as documented, matching the expected behavior described in the issue.Additional instructions:
Fixes #1148
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.