How to get coc.nvim port merged cleanly?

[expipiplus1]

I've made a port to coc.nvim: https://github.com/expipiplus1/vscode-hie-server/tree/coc.nvim

I'm certainly no typescript expert, but would really like to merge the support for coc.nvim into master to avoid all the fuss of porting features back and forth. Can any typescript experts lend any advice?

Some things I noticed:

• There's no window, so that prevents quite a few things mapping (things such as the docbrowser) cleanly (these have been disabled for now in my branch).
• The registerCommand (or registerTextEditorCommand (missing)) commands have a slightly different interface, vscode passes editor and edit to them, where as the equivalents have to be fetched from the global workspace in coc.nvim
• No difference between range and vsrange
• Different modules are used for importing (duh)
• strings used instead of Uris

This repository certainly isn't the place for some "compatibility layer", but perhaps if the differences are small enough then this could be done all locally.

[expipiplus1]

One thing might be to encourage contributors to make the same change to the coc.nvim branch when making a PR here; definitely not an ideal solution though.

[expipiplus1]

Bumped into this "compatibility layer" https://github.com/coc-extensions/coc-fsharp/blob/30b93e1071d87361f5690ddd9fbe4e3a2fca84fb/client/coc_compat.ts

Perhaps we could merge something like this and the fork would just be fiddling with some imports at the top. It would certainly make the rebases I'm doing less painful.

[fendor]

@expipiplus1 Is this still something you want to pursue?

[expipiplus1]

It seems that in the intervening 3 years things have changed and this doesn't seem to be necessary any more, or at least I've stopped using whatever features it provided haha. Someone else can reopen it if they care :)