References to submodules with backticks and @{tag} about ldoc HOT 3 CLOSED

I think the latest push should sort out the issue. It came as a surprise to me, but @{mod} wasn't implemented properly! It was finding the module object and then didn't know how to turn it into a reference.

from ldoc.

Actually, the latest push indeed fixed some odds. And that's perfect. Huge thanks for that.
Although the initial problem remains unsolved, but I do have the feeling I haven't stated my point incorrectly.
Here is an example.
In lib.lua, the description for lib.newLog function has a inlined reference (with backticks) to the module core.log, but the generated documentation won't convert that reference into an HTML link, but just wrap it into <code></code> tags.
Well replacing log with core.log produces the desired output, and that's normal, as the very name of the inner submodule is core.log. But keeping it as it is makes it easier to read, instead of writing:

--- Returns a `core.log` instance.
-- @treturn log a `core.log` instance
function lib.newLog() ... end

from ldoc.

It is a little hard to tell since the MWE repository has been removed, but it seems to me that needing the fully qualified module name is expected. If the only remaining thing here is a request for a shortcut way of reaching submodules, I think I'm going to suggest that's not a great idea for long term maintainability. I would be too easy to get things cross-wired if the module was ever refactored and not notice the problem.

If there is something else I'm missing feel free to comment for re-evaluation. Alternatively if anybody has a PR they think is an improvement that doesn't break anything else I'd definitely consider the use case.

from ldoc.