You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(amazonq): stop workspace indexing in extension (aws#7197)
## Problem
- we don't need workspace indexing on extension side anymore,
the `isVectorIndexEnabled` setting controls if we build vector index
used for @workspace feature, since now chat is moving to language
server, the extension side workspace lsp should be only responsible for
building BM25 index for inline, and not responsible for vector indexing
for chat.
## Solution
- stop vector indexing on extension
- next step is to tie workspace index setting to language server
workspace indexing, will be in next PR
---
- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.
0 commit comments