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
I am using the plain api-documenter markdown command line and processing the output with github pages' jekyll processing.
This seems to work pretty well except for a couple of weeks now it's unable to correctly detect the entrypoint links into the docs.
So rather than showing a table with links it's showing the undecoded markdown.
meaning that unless the final jekyll markdown processor understood markdown within html tags this is not going to work.
Repro steps
All I have to do is execute api-extractor and api-documenter and deploy the result.
Expected result:
Normally I would expect this to work normally and it used to.
Actual result:
Now it's not linking correctly, but the rest of the content looks good.
Details
Rather than rendering <a> links the jekyll renderer is not recognizing [...](...) and outputting it verbatim. I am suspecting since it's a table it's expecting additional spacing or something silly like that.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
Summary
I am using the plain api-documenter markdown command line and processing the output with github pages' jekyll processing.
This seems to work pretty well except for a couple of weeks now it's unable to correctly detect the entrypoint links into the docs.
So rather than showing a table with links it's showing the undecoded markdown.
This looks like this
here is the current URL this is running under https://lukso-network.github.io/tools-data-providers/
The compiled "markdown" file contains
meaning that unless the final jekyll markdown processor understood markdown within html tags this is not going to work.
Repro steps
All I have to do is execute api-extractor and api-documenter and deploy the result.
Expected result:
Normally I would expect this to work normally and it used to.
Actual result:
Now it's not linking correctly, but the rest of the content looks good.
Details
Rather than rendering
<a>
links the jekyll renderer is not recognizing[...](...)
and outputting it verbatim. I am suspecting since it's a table it's expecting additional spacing or something silly like that.Standard questions
Please answer these questions to help us investigate your issue more quickly:
@microsoft/api-documenter
@microsoft/api-extractor
[email protected]
node -v
)?The text was updated successfully, but these errors were encountered: