esensar / esensar/neovim-java

Move neovim extension MsgPack types support to core-rpc

Open
#121 1 comment 0 reactions 0 assignees View on GitHub
core-rpc enhancement neovim-api stale
Dominant language
Java
Stars
55
Forks
9
PR merge metrics
No merged PRs in 30d

Description

Currently, `neovim-api` module introduces support for Neovim extension types, meaning to use them in `core-rpc` or other modules which don't depend on `neovim-api`, custom implementation is needed. Besides this, this makes usage of library in some cases needlessly complicated (`ReactiveRpcClient` and `RpcClient` don't support these types by default, meaning custom instances need to be created to be used in `neovim-api` module). `NeovimApis` makes it easier for some cases, but ideally it should not be possible to build these clients without support for neovim types (or should not be the default behavior at least).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.