Closed very-doge-wow closed 9 months ago
Interesting. Do you have a test repo you can share so I can reproduce it? It's ok if it's a private one, you can share it directly with me. It would help a lot!
Currently I don't have a sample repo as the doc I'm creating is inner source of my corporation. But you can provoke it in any docusaurus project with the plugin by simply adding a line like this to an MD doc:
%%CI/CD|cicd%% test test test [test](https://github.com/)
test test
Here's a screenshot of the issue I mentioned. As you can see the backticks aren't interpreted but rather just rendered as plaintext.
Need to look at it - sorry lack of time right now
@LunaticMuch Any progress?
@LunaticMuch Any updates?
@LunaticMuch Are you still maintaining this repository? I'm not giving up :smile:
@very-doge-wow I get you are not giving up, but you are also not getting how it works. Spamming messages does not help. You got asked for a reproducible test case, which you did not provide. You possible test actually does not trigger the error. I can render perfectly the line you provided.
No need to get passive aggressive, I do get how it works. However you said you simply needed time to work on the issue, but I never received any updates. All I did was ask if you already had made any progress, no more or less. Wasn't even meant as critisism but rather just wanted to know the status.
First of all, thanks for the plugin, works really well.
The problem I have is this: When using a term inside MD elements such as lists or tables, after parsing (i.e. when the syntax has been replaced with the react component) all text in the same line behind the react component is no longer interpreted as markdown and variables in codeblocks are tried to be interpreted instead of rendered as codeblock.
Here's an example:
After parsing and then building the documentation, the codeblock is not rendered but gives an error during build. How can this be fixed?