Skip to content

Conversation

keegancsmith
Copy link
Member

@keegancsmith keegancsmith commented Mar 27, 2023

Previously we silently ignored it. For example a search like (foo))
would just work since we would only parse (foo). We now report back to
the user the problem.

Note: we already had special handling for unbalanced parenthesis like
this ((foo).

Test Plan: added more test cases. Especially tried to explore areas we
could validly not consume the whole input but couldn't find one.

Fixes #547

Previously we silently ignored it. For example a search like `(foo))`
would just work since we would only parse `(foo)`. We now report back to
the user the problem.

Note: we already had special handling for unbalanced parenthesis like
this `((foo)`.

Test Plan: added more test cases. Especially tried to explore areas we
could validly not consume the whole input but couldn't find one.
@keegancsmith keegancsmith changed the title wip handle parse function not consuming all of input query: handle parse function not consuming all of input Jun 27, 2025
@keegancsmith keegancsmith requested a review from a team June 27, 2025 15:09
@keegancsmith keegancsmith marked this pull request as ready for review June 27, 2025 15:09
@keegancsmith keegancsmith merged commit a4188d2 into main Jul 14, 2025
11 checks passed
@keegancsmith keegancsmith deleted the k/unbalanced-paren branch July 14, 2025 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Errors for queries with imbalanced parentheses are reported only for too many left parentheses
2 participants