Open
Conversation
Previously, when both scope=true and regex=true were set, the scope branch
always used literal search (searchContentWithScope), ignoring the regex flag.
The branch order in handleSearch was: if (scope) {literal only} else {regex/literal}.
Now restructured to 4-way branch:
1. scope && regex -> searchContentRegexWithScope (NEW)
2. scope -> searchContentWithScope (unchanged)
3. regex -> searchContentRegex (unchanged)
4. default -> searchContent (unchanged)
Added searchContentRegexWithScope public method and
searchInContentRegexWithScope private helper to Explorer, using trigram
acceleration and regexMatch per-line with scope lookup.
Benchmark Regression ReportThresholds: 10.00% and 50,000 ns absolute delta
|
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
1 participant
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.
Summary
Prepare hotfix release 0.2.5791 by bumping the embedded release version on the release branch.
Context
This PR merges the
release/0.2.5791-hotfixbranch back intomainso the hotfix release metadata is aligned on the default branch.Changes
0.2.579to0.2.5791.Key Implementation Details
The net change currently visible against
mainis limited tosrc/release_info.zig, which controls the release semver reported by the binary.Testing
Reviewers can verify with:
zig build test python3 scripts/e2e_mcp_test.py --binary zig-out/bin/codedb --project /path/to/codedbLinks
release/0.2.5791-hotfix