fix: remove default file intent from search - #37
Merged
Merged
Conversation
Stop forcing production-only file intent on unified search and legacy symbol search now that backend relevance is stronger without the client-side filter. Keep code-navigation request debugging available with a safe shape logger and an explicit-only wire logger so exact GraphQL payloads are inspectable when backend issues recur.
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
searchand legacysearch_symbols/githits code searchto production-only file intent so omitted intent sends no filtercode-navrequest-shape logger and an explicit-onlycode-nav-wirelogger for exact GraphQL payloadsValidation
bun run typecheckbun test src/shared/debug-log.test.ts src/services/code-navigation-service.test.ts src/commands/search.test.tsbun run build