Strip quotes from quoted module names, like module:"core.lang"

[evil-shrike]

I have some modules (AMD) with "." in their name (like "core.lang.js" in the example below).
I can see two options: put module name in quotes and do not do this.
If I skip quotes in @export (in core.lang.js) and in @type (in core.js) (see #1 in the code) then generated doc will contain:

• Index: lang in Module, link leads to lang.html (ok)
• module-core.html: lang :module:core.lang where link module:core.lang leads to module-core.html#lang (wrong!)

If I put quotes (see #2 in the code) then generated doc will contain:

• Index: "core.lang" in Module (with quotes!) leads to _.html (wrong!)
• module-core.html: lang :module:"core.lang" where link module:"core.lang" leads to _.html (wrong!)
• .html is actually page for core.lang module, but obviously it should not be named ".html"

So none of cases (with and without quotes) works correctly.

core.lang.js:

define([], function () {
    /**
     * #1: @exports core.lang
     * #2: @exports "core.lang"
     */
    var lang = {
        /**
         * Defines a class
         * @returns {Function}
         */
        Class: function () {    }
    };
    return lang;
});

core.js:

define(["core.lang"], function (lang) {
    /**
     * @exports core
     */
    var core = {};

    /**
     * base language helpers
     * #1: @type module:core.lang
     * #2: @type module:"core.lang"
     */
    core.lang = lang;

    return core;
});

[hegemonic]

Using quotes is the right way to document this. The fix is to update the template (and related code) to strip the quotes from names.

[yurijmikhalevich]

This issue is really critical. Voting for it with my comment.

[froodian]

Agreed

[jeroenvollenbrock]

Is there any news on this? Would a PR help to speed this up?