jgleitz / markdown-it-kbd Goto Github PK

This issue provides visibility into Renovate updates and their statuses. Learn more

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): lock file maintenance

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• chore(deps): update dependency marked to 4.0.10 [security]

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency eslint to v8

• Check this box to trigger a request for Renovate to run again on this repository

I'm trying to fork your code to add attributes to the kbd tag (classes or data-attr). However I'm very green in my markdown-it plugin writing and am having trouble. I'm wondering if you know of how I could do like

[[x CLASSNAME]]

which would render

<kbd class="CLASSNAME">x</kbd>

I'd potentially want to allow multiple attributes but I figure this is an easy example to start.

I've started using your extension for live previewing of my mkdocs-based documentation. It's awesome, thank you!

I bumped into a small issue with kbd. The pymdown-extensions syntax is ++Ctrl+Esc++, while yours is [[Ctrl+Esc]].
I didn't find any other syntaxes online regarding kbd, so I can't say which one is better.
But currently I can either preview in vscode, OR have the correct results in mkdocs.

Would it be possible to either agree in a common syntax for this, or to support both of them?
I also filed a similar issue in pymdown-extensions: facelessuser/pymdown-extensions#1517

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

According to the spec (HTML5 kbd spec), kbd elements are nested to represent keycaps as in:

<p>To make George eat an apple, press <kbd><kbd>Shift</kbd>+<kbd>F3</kbd></kbd></p>

but this does not work:

To make George eat an apple, press [[[[Shift]]+[[F3]]]]

results in:

<p>To make George eat an apple, press [<kbd>[Shift</kbd>+<kbd>F3</kbd>]]</p>

At the moment, “[[” and “]]” are not allowed within keystroke tags, because I can't think of a way to handle this that would make sense in all scenarios. If you think you know how it should be done, please file an issue!

What about escaping? So that would be [[\]\]]] and [[\[\[]] respectively. Not sure how one would implement this, though.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.