You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In making a document which also works on npmjs.com, we need support for links which are prefixed with user-content-. GitHub supports this prefix in addition to unprefixed ones, while npmjs.com requires it.
For example with eslint-plugin-jsdoc, the Markdown Settings heading gets turned into the anchor user-content-settings, and the HTML anchor eslint-plugin-jsdoc-settings becomes user-content-eslint-plugin-jsdoc-settings with no other anchors available.
I'm guessing the article ID passed on to your contents generators may need to be prefixed with user-content-.
In making a document which also works on npmjs.com, we need support for links which are prefixed with
user-content-
. GitHub supports this prefix in addition to unprefixed ones, while npmjs.com requires it.For example with
eslint-plugin-jsdoc
, the MarkdownSettings
heading gets turned into the anchoruser-content-settings
, and the HTML anchoreslint-plugin-jsdoc-settings
becomesuser-content-eslint-plugin-jsdoc-settings
with no other anchors available.I'm guessing the article ID passed on to your contents generators may need to be prefixed with
user-content-
.This would fix our gajus/eslint-plugin-jsdoc#707
The text was updated successfully, but these errors were encountered: