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

Propagation of Attributes in Markdown-it-container #111

Closed
StefanZander opened this issue Jul 31, 2020 · 3 comments
Closed

Propagation of Attributes in Markdown-it-container #111

StefanZander opened this issue Jul 31, 2020 · 3 comments

Comments

@StefanZander
Copy link

StefanZander commented Jul 31, 2020

I am using both extensions markdown-it-attrs and markdown-it-container in conjunction with Marp in order to create and render my lecture slides using markdown.

When combining both extensions, e.g.,

::: definition
some def text...

Source: some source text {.source}
:::

the .source class will be propagated to the definition container (the parent div) rather than to the paragraph that represents the source text.

The problem as described in Post 1 in Issue #72 is still present to me.

I also tried the workaround proposed by @mb21 in Issue #72 but it does not work in my setup.

Since I really like both extensions, I hope there is another way of making both work together.

Thanks in advance.

@arve0
Copy link
Owner

arve0 commented Sep 13, 2020

Hi! I'm sorry, but I do not have time to debug your bug. If you find out that the error is on markdown-it-attrs, I would be glad to get an update.

@thom4parisot
Copy link

I opened a pull request with a failing test case.

I have not figured out yet if it's a bug, or a missing feature.

What's tough thoug, is this syntax is added via an additional plugin, it's not part of markdown-it core 😶‍🌫️

@arve0
Copy link
Owner

arve0 commented Dec 30, 2021

Hi 🙂 Sorry to inform that I do not have time to investigate this issue. Feel free to reopen issue if you want to take a stab yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants