Skip to content
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

Markdown plugin name only works in the short-hand form #2286

Closed
1 task done
vojtapol opened this issue Apr 7, 2020 · 2 comments · Fixed by #2289
Closed
1 task done

Markdown plugin name only works in the short-hand form #2286

vojtapol opened this issue Apr 7, 2020 · 2 comments · Fixed by #2289
Labels
type: bug Something isn't working

Comments

@vojtapol
Copy link

vojtapol commented Apr 7, 2020

  • I confirm that this is an issue rather than a question.

Bug report

Steps to reproduce

When configuring Markdown and requesting a plugin to be used like this:

markdown: {
  plugins: [
    'markdown-it-abbr'
  ]
}

The abbreviations are ignored.

However, this configuration works as desired:

markdown: {
  plugins: [
    'abbr'
  ]
}

What is expected?

Both markdown-it-abbr and abbr in the plugin section should have the same effect as according to the documentation omitting the markdown-it- portion of the plugin name is optional.

What is actually happening?

Only the shorthand form works.

Other relevant information

My package.json:

{
  "name": "wiki",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "docs:dev": "vuepress dev docs",
    "docs:build": "vuepress build docs"
  },
  "devDependencies": {
    "@vuepress/plugin-back-to-top": "^1.4.0",
    "markdown-it-abbr": "^1.0.4",
    "vuepress": "^1.4.0"
  }
}
@meteorlxy meteorlxy added the type: bug Something isn't working label Apr 8, 2020
@meteorlxy
Copy link
Member

Thanks for report.

@meteorlxy
Copy link
Member

Ref #2175

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants