Skip to content

Commit

Permalink
Combine completer and renderer into one module
Browse files Browse the repository at this point in the history
My attempt to completely decouple this two is failed, so it is better to
just combine them to simplify codebase.
  • Loading branch information
monkoose committed Sep 16, 2024
1 parent af3d382 commit 110abba
Show file tree
Hide file tree
Showing 6 changed files with 472 additions and 555 deletions.
15 changes: 0 additions & 15 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -453,21 +453,6 @@ your code base. When you switch buffers, this context should be updated
automatically (it takes some time). You can see current chat context in the
left bottom corner.

### 🚗 Roadmap

- [x] Add vimdoc help
- [x] Add the command to open buffer with the log output
- [x] Add :checkhealth
- [x] Add support for Codeium Chat (in browser only)
- [ ] Completely decouple renderer from completer.
Add an custom renderer setup option.
Renderer is already pretty much decoupled, but still transforms data it receives and
so completer receives from it more data than required. Its API should
consist of: display(), update() and clear() methods and do not pass any data to
the completer. Not sure if someone will use it, but there are always some enthusiasts and hackers.
With this feature implementing some custom renderer (like for any extendable completion engine) would be easy.
Provide an example of custom renderer with built-in completion (omnifunc).

### 💐 Credits

- [codeium.vim] - The main source for understanding how to use Codeium.
Expand Down
Loading

0 comments on commit 110abba

Please sign in to comment.