Include inline completions in @vscode/chat-lib #1343
Draft
Conversation
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
jeffreyhunter77
force-pushed
the
chrmarti/chat-lib-inline-completions
branch
from
eef1198 to
1dc680f
Compare
…mas for dependency extraction
jeffreyhunter77
force-pushed
the
chrmarti/chat-lib-inline-completions
branch
from
1dc680f to
17fc7c7
Compare
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.
WIP for including inline completions in @vscode/chat-lib.
Initially we might be able to just reexport
getInlineCompletionsfrom the library because that expects objects of types the CLS also has. I have updated the extraction script to also follow#lib/and similar imports.Setup:
Extract and compile:
This currently shows compile errors. One issue appears to be that the completions code reaches back to
#bridges/which then reaches into completions extension code. The extraction script follows all these code references and ends up extracting extension code we don't need in the library and that doesn't compile without the VS Code API. Maybe the direct references to#bridges/can be avoided.Once it compiles, tests can be run: