Resolve case-sensitivity in QueryParser to support Chapters/Members search

[saichethana28]

Proposed change

Resolves #3791

Fixed the logic in query_parser.py to resolve the reported blocker regarding search query processing. The changes ensure that query tokens are handled with proper case integrity and logical structure, preventing the parser from failing on specific edge cases.

Changes included:

• Refactored token handling in backend/apps/common/search/query_parser.py.
• Added and updated unit tests in backend/tests/apps/common/search/query_parser_test.py to verify the fix and ensure no regressions.
• Verified that all backend tests pass and coverage is maintained.

Checklist

• Required: I followed the contributing workflow
• Required: I verified that my code works as intended and resolves the issue as described
• Required: I ran make check-test locally: all warnings addressed, tests passed
• I used AI for code, documentation, tests, or communication related to this PR

[coderabbitai]

Summary by CodeRabbit

• Bug Fixes

  • Improved structured search query parsing to properly handle case sensitivity.

• Tests

  • Added test cases validating parsing of quoted multi-word search values and case sensitivity behavior in query operations.

Walkthrough

The changes add test coverage for QueryParser case sensitivity handling and configure the structured search to use case-sensitive parsing mode to preserve field value casing while normalizing field names.

Changes

Cohort / File(s)	Summary
Query Parser Tests backend/tests/apps/common/search/query_parser_test.py	Added two test cases: test_quoted_multi_word_values verifies parsing of quoted multi-word fields with lowercasing in non-case-sensitive mode; test_case_sensitivity_toggle verifies case preservation when case_sensitive=True.
API Search Configuration backend/apps/api/rest/v0/structured_search.py	Modified QueryParser instantiation in apply_structured_search to pass case_sensitive=True, enabling preservation of original field value casing.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• Implemented Initial Query Parser for Search Interfaces #2114: Implements QueryParser with case_sensitive option parameter and corresponding test coverage that this PR activates.

Suggested reviewers

• kasya

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title 'Resolve case-sensitivity in QueryParser to support Chapters/Members search' directly and specifically addresses the primary change: fixing QueryParser case-sensitivity behavior.
Description check	✅ Passed	The PR description is related to the changeset, referencing issue #3791 and describing changes to query_parser.py and test files.
Linked Issues check	✅ Passed	The PR changes align with issue #3791 requirements: enabling case_sensitive=True in structured_search.py and adding tests to verify case preservation behavior.
Out of Scope Changes check	✅ Passed	All changes are directly related to resolving the QueryParser case-sensitivity issue; test additions and parser configuration changes are within scope.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

backend/tests/apps/common/search/query_parser_test.py (2)

212-218: Good coverage for multi-word quoted values.

Consider also asserting the field and type keys (e.g., results[0]["field"] == "project") to guard against regressions in field parsing alongside the value check. This is optional.

---

220-223: Test named "toggle" but only verifies the case-sensitive path.

To live up to the name "toggle", consider also asserting the non-case-sensitive parser lowercases the same value, and that the field name is normalized to lowercase in both cases. This strengthens the test as a true contrast.

♻️ Suggested enhancement

     def test_case_sensitivity_toggle(self):
         query = "Author:OWASP"
         cs_result = self.case_sensitive_parser.parse(query)
+        ci_result = self.parser.parse(query)
+
+        assert cs_result[0]["field"] == "author"
         assert cs_result[0]["value"] == "OWASP"
+
+        assert ci_result[0]["field"] == "author"
+        assert ci_result[0]["value"] == "owasp"

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

[saichethana28]

Hi @arkid15r, could you please review this? I've fixed the QueryParser case-sensitivity for Chapters/Members. Once this blocker is resolved, I’m ready to start extending structured search to other entities

[saichethana28]

@cubic-dev-ai review this pull request

[cubic-dev-ai]

@cubic-dev-ai review this pull request

@saichethana28 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

1 issue found across 3 files

Confidence score: 3/5

• The change in backend/apps/common/search/query_parser.py ignores the case_sensitive flag for string values, which can break expected case-insensitive search behavior for users.
• This carries some user-impacting regression risk, so the merge risk is moderate despite being a localized change.
• Pay close attention to backend/apps/common/search/query_parser.py - case_sensitive is no longer applied to string query inputs.

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="backend/apps/common/search/query_parser.py">

<violation number="1" location="backend/apps/common/search/query_parser.py:191">
P2: The `case_sensitive` parameter is now ignored for string values, likely breaking case-insensitive search behavior.

Previously, `query = query.lower()` ensured that if `case_sensitive=False` (the default), all inputs were lowercased. By removing this global normalization without adding value-specific normalization in `parse` or `to_dict`, the parser now preserves the case of values (e.g., `Title:Value`) even when `case_sensitive` is `False`.

This changes the contract of the class and may regress existing search functionality that expects case-insensitive normalization.

**Fix Suggestion:**
Apply lowercasing to string values when `case_sensitive` is `False`.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[saichethana28]

@cubic-dev-ai review this pull request

[cubic-dev-ai]

@cubic-dev-ai review this pull request

@saichethana28 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 3 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

[saichethana28]

@arkid15r, let me know if this looks good to you or if any changes are needed

[sonarqubecloud]

❌ The last analysis has failed.

See analysis details on SonarQube Cloud

[arkid15r]

Would this work?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.68%. Comparing base (6c59166) to head (8e2ba2c).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3844   +/-   ##
=======================================
  Coverage   93.68%   93.68%           
=======================================
  Files         463      463           
  Lines       14420    14420           
  Branches     1939     1939           
=======================================
  Hits        13509    13509           
  Misses        535      535           
  Partials      376      376           

Flag	Coverage Δ
backend	95.65% <100.00%> (ø)
frontend	88.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
backend/apps/api/rest/v0/structured_search.py	100.00% <100.00%> (ø)

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c59166...8e2ba2c. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[saichethana28]

Would this work?

Yes, this works. Moving the .lower() call to the start of the parser is a much cleaner optimization. Since structured_search.py explicitly passes case_sensitive=True, it correctly skips that block and preserves the casing for Chapter names. The refactor looks solid