-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update mini.doc to LuaCATS #666
Comments
Thanks for the suggestion! On first glance, this makes sense. Having some strict rules from 'lua-language-server' is good. I'll look into it (not very soon, I am afraid). |
I'll give a shot as well. Instead of manually parse annotations line (the one starting with ./lua-language-server --doc=path/to/lua/workspace I know that it's a bit against the mini.doc philosophy (few dependencies as possible, here we depend on lua LSP) but this should ensure perfect annotations parsing. So it "just" remains to convert json to proper vim documentation for :help |
No, that is definitely against 'mini.nvim' design. Everything will be parsed without external dependencies. |
Let's use this as a tracking issue to gather other similar suggestions for 'mini.doc' improvements that are related to LuaCATS specifications. In particular:
|
Contributing guidelines
Module(s)
mini.doc
Description
LuaLS/lua-language-server is the most used implementation Language server for Lua. One of its features are annotations implemented as
LuaCATS
(Lua Comment And Type System). As stated in their docs:The current implementation of
mini.doc
try to parse EmmyLua-like annotations. Compare to EmmyLua annoation,LuaCATS
define a precise specification for annotation.For instance, the
mini.doc
:help section mentions:Conversely, the
@param
annotation supported by LuaLS/lua-language-server is explicitly defined as:In this format, the
type
directly follows the parametername
, eliminating the need for heuristic searches for the type. Additionally, this format simplifies the integration of user-defined types into help.txt.While I could develop my own hooks to adhere to the
LuaCATS
specification (skill permitting), I believe that aligning with a dominant and well-documented standard would be more advantageous for the community.The text was updated successfully, but these errors were encountered: