fix: added fix for free text with quick filter issue

[ahrefabhi]

📄 Summary

---

✅ Changes

• Added fix for free text with quick filters issue.

Screen.Recording.2025-12-03.at.6.03.26.PM.mov

---

Note

Improves query parsing to retain incomplete free-text keys and updates filter value conversion to unquote quoted strings; adds a unit test for the scenario.

• Query parsing (frontend/src/utils/queryContextUtils.ts)
  • Finalize current pair on conjunctions or new KEY tokens (regardless of completeness) to support free-text preceding valid filters.
• Filter value formatting (frontend/src/components/QueryBuilderV2/utils.ts)
  • formatSingleValueForFilter now returns unquoted strings when values are quoted (via isQuoted/unquote).
• Tests (frontend/src/utils/__tests__/queryContextUtils.test.ts)
  • Add test covering free-text followed by NOT IN list parsing.

^{Written by Cursor Bugbot for commit 73fdacf. This will update automatically on new commits. Configure here.}

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: Incomplete pairs create malformed filters with empty operators

The removal of isQueryPairComplete(currentPair) allows incomplete query pairs (free text without operators) to be returned by extractQueryPairs. However, convertExpressionToFilters processes all pairs without checking isComplete, creating filters with empty operators and values. When these filters are later converted back to expressions via convertFiltersToExpression, it produces malformed expressions like "keyname ''" (double space with empty quoted value), which could cause parsing errors or unexpected query behavior downstream.

Additional Locations (1)

• frontend/src/components/QueryBuilderV2/utils.ts#L197-L213