feat: pass in a custom request to use instead of default LSP's about otter.nvim HOT 5 OPEN

Ah, I belive you are talking about the handler?Those are a bit harder to make configurable, because some require speciel treatement (e.g. we use our own hover handler because the default nvim one doesn't like hovers responses that originate from another buffer)

from otter.nvim.

I see! Thanks for taking the time to answer at that hour of the night :)

from otter.nvim.

For some requests your custom handlers may work out of the box. You can experiment with using the otter.keeper.send_request function directly (e.g. by copy-pasting one of the ask_... functions for your own needs). Because for some requests all the necessary changes are already done in the filter function, while others required special treatment of the handler itself (like hover).

Maybe we can identify parts of handlers that can safely be exchanged and thus be made configurable more easily.

from otter.nvim.

I just merged a big rewrite. Depending on the nature of your usual type_defintion function, it should now just work or be apparent why it doesn't currently (see https://github.com/jmbuhr/otter.nvim?tab=readme-ov-file#current-limitations)

from otter.nvim.

Hey Jannik, sorry for the late reply, I'm drowning in work.
Thanks a lot for all that you do and for this great tool :)
I'll check it out!

from otter.nvim.