-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make @link tag display more friendly #738
Comments
When this option is set to `true`, the `{@link}`, `{@linkcode}`, and `{@linkplain}` tags will use the short name, not the longname, as the link text. For example, `{@link foo.bar.baz}` will result in the link text `baz`. This option has no effect when link text is provided as part of the tag (for example, `{@link foo.bar.baz My link text here}`). As part of this change, I also simplified many of the tests for the `resolveLinks` method.
Fixed on master. The fix will be included in JSDoc 3.6.0. To enable this feature, set the value This setting has no effect when you include link text with the |
* master: (95 commits) update dependencies and supported Node.js versions 3.5.5 changelog Prefer copyFileSync from here over native (jsdoc#1440) upgrade Babylon fix test breakage 3.5.4 changelog prevent crash when an anonymous class is passed as a parameter (jsdoc#1416) hide the signature in the heading for classes with hidden constructors (jsdoc#1397) chore(package): update nyc to version 11.1.0 (jsdoc#1417) add `templates.useShortNamesInLinks` config option (jsdoc#738) allow users to specify a highlighter for Markdown code blocks (jsdoc#1412) document `longnamesToTree`, plus other doc improvements (jsdoc#43) move namespaces and interfaces up in the nav (jsdoc#1410) don't pretty-print code blocks that begin with "```plain" (jsdoc#1361) improve comment make the `exports` tag work correctly when combined with the `enum` tag (jsdoc#970) fix Node.js 4.x update tested Node.js versions use the markdown-it Markdown parser by default (jsdoc#1243) enable more Babylon options (jsdoc#1411) ... # Conflicts: # .travis.yml # README.md # lib/jsdoc/src/astbuilder.js # lib/jsdoc/src/visitor.js # lib/jsdoc/util/markdown.js # lib/jsdoc/util/templateHelper.js # package.json
When we have jsdoc as:
The output could be:
In practice, we'd like to see just:
or
The text was updated successfully, but these errors were encountered: