Closed atengberg closed 1 year ago
Additionally if a header format could be specified for the did files, those two could be linked to avoid duplication of documentation.
Here is the relevant doc comment formatting logic:
The "go-to-definition" logic (for pointing to other doc comments) is implemented here:
Because doc comments are currently discovered via AST traversal, the language server might need some refactoring to fully achieve what you're suggesting. Feel free to create a docs.ts
file for any required helper functions, and I'll eventually move the rest of the onHover()
logic into this file as well.
I would also recommend turning on "Debug Hover" in the extension settings, which shows some additional AST information in the hover tooltips.
Let me know if you run into any roadblocks, and I'll do my best to help out.
Closing as not currently planned (feel free to reopen individual requests with more details if needed).
Could someone could point me to the file that handles the "Motokodoc" formatting and logic (particularly for the tooltip popup on hover that shows up when a field as the Motokodoc comment header)?
In particular I'd like to add autogeneration/highlighting for argument and return signature, as well the ability to point the comment to another Motokodoc comment.