Open dvcrn opened 2 years ago
That's soooooo weird, I have never come across that!
You see, from the perspective of the extension developer, we actually have little control on how these things are displayed: this comes directly from gopls
and is fed straight into Nova. The extension doesn't have a way to know what gopls
is passing to Nova in this case, much less the ability to change what is returned by gopls
(or, if there is a way, it's unknown to me).
The only explanation I can come up with is that some of the comments on some of your functions have Markdown in them (which should _ be a problem!) and that the Markdown parser used by Panic gets seriously confused because of that. This is just a wild speculation based on some comments made by @logan (he's with Panic's development team), who remarked — a few major versions ago! — that the Markdown parser wasn't yet 'very ready'...
On the other hand, the current Nova version is supposed to have a newer/better Markdown renderer, and I haven't seen anything like that!
Do you usually use Markdown inside your own comments?
And what version of Nova and gopls
are you using?
I'm just trying to eliminate some of the most trivial problems first... mostly to see if I can at least replicate it.
Thanks for the reply! Good theory, but no I don't use any markdown in my comments or doc strings 😅
All I did was setup nova, setup lsp and try to use it on an existing project
I wonder if you still have that issue?...
I'm getting a bunch of these:
Some functions have their name in really big letters, some others don't have a name at all and only display from the arguments onwards