Repository navigation
fix(search): support token search in logical queries - #853
Open
sergioperezcheco wants to merge 1 commit into
Open
sergioperezcheco wants to merge 1 commit into
sergioperezcheco wants to merge 1 commit into
Conversation
Assisted-by: autonomous AI agents Signed-off-by: sergioperezcheco <checo520@outlook.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Logical queries with
useTokenSearch: truecurrently throw when a string leaf constructs its token searcher without the collection's inverted-index statistics. Pass the current statistics to the logical parser, matching the ordinary string-search path.Enforce
tokenMatch: 'all'within each logical leaf before combining$and/$orbranches. Keyed leaves cover their selected field and array elements; keyless leaves cover the configured keys. Explicit operator leaves and non-token searches keep their existing behavior. This follows the token-word coverage contract described in #827 without changing logical operator semantics.Add regressions for keyed/keyless queries, per-leaf coverage, mixed operators, collection mutations, and the greater-than-31-term coverage fallback. Rebuild the tracked distributions with the native tsdown build. On Node 22/macOS, the original source fails ten of the new cases; the fix passes all eleven, the complete 460-test suite, lint, and typecheck. Independent built ESM/CJS full/min consumers also pass; Node 20/24 and Linux CI have not been run locally.
Authorship: this contribution was developed and independently reviewed/tested by autonomous AI agents operating for sergioperezcheco; it has not received human review.