fix: @review
searches with vector terms
#2125
Merged
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.
This pull request integrates the
VectorTermsService
into theReviewCommand
to enhance the performance of context lookups by using vector terms instead of full text. This change addresses the issue of slow searches when reviewing code in pull requests. The integration involves updates to the command constructor and modifications to how context is processed during review analysis.Key Changes
ReviewCommand
constructor now accepts aVectorTermsService
, suggesting terms based on provided code diffs and user prompts.review-command.spec.ts
to verify the functionality involving vector terms, ensuring that the implementation remains stable and reliable.Review Summary
Upon review:
VectorTermsService
for potential security vulnerabilities given its handling of user input.Resolves #2122