| Age | Commit message (Collapse) | Author |
|---|
|
* feat: :construction: use ComboBox in place of UserInputContainer
* feat: :construction: adding context to previous inputs steps
* feat: :sparkles: preview context items on click
* feat: :construction: more work on context items ui
* style: :construction: working out the details of ctx item buttons
* feat: :sparkles: getting the final details
* fix: :bug: fix height of ctx items bar
* fix: :bug: last couple of details
* fix: :bug: pass model param through to hf inference api
* fix: :loud_sound: better logging for timeout
* feat: :sparkles: option to set the meilisearch url
* fix: :bug: fix height of past inputs
|
|
|
|
|
|
* headless IDE subclass
* finish headless_ide methods
* feat: :sparkles: headless mode running with config flag
* work on debugging
* python lsp support
* more lsp+debugging work
* refactor: :safety_vest: safely load LSP
* test: :white_check_mark: testing steps in headless mode
* refactor: :clown_face: cleanup subprocesses
* fix: :bug: handle data: [DONE] from Together
|
|
* refactor: :construction: Initial, not tested, refactor of LLM
* refactor: :construction: replace usages of _complete with complete
* fix: :bug: fixes after refactor
* refactor: :recycle: template raw completions in chat format
* test: :white_check_mark: simplified edit prompt and UNIT TESTS!
* ci: :green_heart: unit tests in ci
* fix: :bug: fixes for unit tests in ci
* fix: :bug: start uvicorn in tests without poetry
* fix: :closed_lock_with_key: add secrets to main.yaml
* feat: :adhesive_bandage: timeout for all LLM classes
* ci: :green_heart: prepare main.yaml for main branch
|
|
|
|
|
|
Fixup search cross workspace polution
|
|
|
|
|
|
|
|
- Added to the build step in the vscode-extension:build task
- Added inline source maps so its easier to track down issues when using console.log / debugger in chrome dev tools within vscode
|
|
|
|
|
|
- Preventing mocha timeouts due to hitting breakpoints
|
|
|
|
Added example directory with a typescript program and open it by default in the extension host - its nice to have an isolated environment where the extension can be played with. You can always open an actual project folder if you want to
|
|
|
|
figure out commands in multiple sub projects. Developers should run this before the first debugging session and anytime they pull
|
|
|
|
|
|
|
