Repository navigation
test(common-utils): cover mixed query operator generation - #3131
Tyagiquamar wants to merge 3 commits into
Conversation
|
@Tyagiquamar is attempting to deploy a commit to the HyperDX Team on Vercel. A member of the Team first needs to authorize it. |
|
|
PR Review
1 finding(s): 🔴 0 P0/P1 · 🟡 0 P2 · 🔵 1 P3 Already reported on an earlier push — no new comments. 1 unchanged from an earlier push (already inline above). Priority comes from a separate grading pass over the finished review. P3 is folded here instead of posted inline. No finding blocks merge automatically; a maintainer decides. |
Deep Review✅ No critical issues found. This PR is tests-only (+97 lines to 🟡 P2 — recommended
🔵 P3 nitpicks (1)
Reviewers (5): correctness, testing, maintainability, project-standards, previous-comments. Testing gaps: The second No finding blocks merge automatically. A maintainer will expect P0/P1 findings in code this PR changes to be fixed; P2/P3 are your call -- fix or reply. Never fix findings about surrounding code here; reply instead. Do not widen the PR. How to respond |
|
@Tyagiquamar the review bot raised some valid comments to review. I also commented on the issue: #3032 (comment) |
|
Updated in b19515c to the tests-only baseline you requested. The existing SQL/English table now covers 16 mixed-operator, explicit-parenthesis, symbolic, implicit, and negation cases. Query generation is unchanged from before this PR. Docker formatting, lint, type checking, package build, and all 421 query-parser tests pass. |
Adds baseline coverage for query generation before changing mixed-operator behavior, as requested in #3032. The PR now changes only tests, so existing saved searches and dashboards keep their current query generation.
Adds 16 cases to the existing SQL and English explanation table: mixed AND/OR chains, explicit grouping on either side, symbolic operators, implicit AND, infix NOT/AND NOT/OR NOT, leading NOT, and negated fields. Removes the previous grouping implementation and duplicate test harness. The behavior fix remains for a separate decision after this baseline is established.
Validated in Docker with Node 22.23.1 and Yarn 4.13.0:
yarn workspace @hyperdx/common-utils tsc --noEmitpassed.yarn workspace @hyperdx/common-utils buildpassed, including declaration generation.yarn workspace @hyperdx/common-utils jest src/__tests__/queryParser.test.ts --ci --coverage=false --runInBand --silent --verbose=falsepassed all 421 tests.yarn lint-stagedpassed for both staged files.Related to #3032. This tests-only PR does not fix the underlying issue or require a release changeset.