The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 4, 2026 7:05am

PR Summary

Low Risk
Low risk: this is an error-handling change that reclassifies certain malformed filter/sort inputs from 500 to 400 with clearer messages; main impact is client-visible status/message changes.

Overview
Fixes row query endpoints to treat malformed caller-supplied filter/sort as client errors instead of server errors.

Introduces TableQueryValidationError in lib/table/sql.ts and throws it from buildFilterClause/buildSortClause (invalid field names, operators, or sort directions), then updates both v0 and v1 table rows GET/PUT/DELETE routes to catch it and return HTTP 400 with the original message (rather than a generic 500).

^{Reviewed by Cursor Bugbot for commit 4306ac7. Configure here.}

Greptile Summary

This PR introduces TableQueryValidationError in lib/table/sql.ts and updates all validation throw-sites (validateFieldName, validateOperator, buildSortClause) to use it, then catches it in all six GET/PUT/DELETE handlers across the v0 and v1 table-rows routes, returning HTTP 400 with the original message instead of a generic 500. The programmer-error default branch in buildFieldCondition correctly retains a plain Error (→ 500), and all JSDoc @throws tags were updated to reference the new subclass.

Confidence Score: 5/5

Safe to merge — targeted, well-scoped fix with no logic regressions or security concerns.

All changed paths are confined to error-path handling. The new error class is minimal and correctly subclasses Error. The programmer-error default case is intentionally kept as a plain Error (→ 500). All six route-handler catch blocks are consistently updated. No P1/P0 findings.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Client
    participant RouteHandler as Route Handler (v0/v1)
    participant Service as lib/table/service.ts
    participant SQL as lib/table/sql.ts

    Client->>RouteHandler: GET/PUT/DELETE ?sort=...&filter=...
    RouteHandler->>Service: queryRows / bulkUpdate / bulkDelete
    Service->>SQL: buildSortClause / buildFilterClause
    alt Invalid field / direction / operator (caller error)
        SQL-->>Service: throw TableQueryValidationError
        Service-->>RouteHandler: propagates
        RouteHandler-->>Client: 400 { error: message }
    else Programmer error (switch/ALLOWED_OPERATORS drift)
        SQL-->>Service: throw Error
        Service-->>RouteHandler: propagates
        RouteHandler-->>Client: 500 { error: "Failed to query rows" }
    else Valid input
        SQL-->>Service: SQL clause
        Service-->>RouteHandler: rows / result
        RouteHandler-->>Client: 200 success
    end

_{Reviews (2): Last reviewed commit: "fix(table): revert default-case throw to..." | Re-trigger Greptile}

Thanks for the review. Both findings addressed in 4306ac7:

1. Reverted the default-case throw in buildFieldCondition back to plain Error — that's programmer-error territory (switch / ALLOWED_OPERATORS drift), correctly maps to 500.
2. Updated @throws JSDoc tags on buildFilterClause, buildSortClause, validateFieldName, validateOperator, and buildFieldCondition to reference TableQueryValidationError.

@cursor review

@greptile