Sorry, I found another strange case. You can write...
# dokka
g
Sorry, I found another strange case. You can write a docstring including something like "[Point] [Collector]" meaning that both braced words should be parsed as links to elements
Point
and
Collector
respectively. But no matter what space you put between them until there is no paragraph break between them it will be parsed as a word "Point" with link to
Collector
. I found a workaround by placing any element that is parsed as a space (for example,
<wbr>
,
&#32;
, etc.). But the workaround works in IntelliJ IDEA but not in HTML version. More precisely, in HTML version the links are separated and parsed correctly, but there is no space between them (no matter what space element you put between them). It is a bug, isn't it? Is there any official solution (or at least workaround) for this?
1
P.S. 1.
[Point][Point] [Collector][Collector]
and
[Point][Point] [Collector]
have the same issue: is parsed correctly, but has space only in IDEA. 2.
[Point] [Collector][Collector]
is parsed as two links to
Collectors
with no space between in both IDEA and HTML version. And in IDEA it works a bit… glitchy. (But I understand that it's a question to IntelliJ IDEA team. For now I need a solution for HTML version.)
i
I'll have to investigate this further, but if it happens both in IntelliJ and Dokka, it might be because we are using the same kdoc markdown parser under the hood (Dokka is relying on some compiler/intellij code). If that's the case, there's no quick fix for this About the absence of spaces, that's a known problem, it happens when two non-text markdown nodes are used one after another, i.e
Copy code
/**
 * _hello_ *there*
 */
fun test() {}
will result in
_hello_*there*
That's also related to the markdown parser and is not as easy to fix 😞 but we'll get to this one for sure
And the incorrect links (
[Point] [Collector][Collector]
), where
Point
leads to
Collector
is something I'm not aware of and I'm not sure what it might be related to 😞 Feel free to create an issue about this, it needs to be looked at and fixed IDEA seems to be liking to correct declarations in this case
m