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

Markup is not rendered correctly issues with comments and links #1390

Closed
Siegfriedk opened this issue Dec 16, 2019 · 3 comments · Fixed by #1476
Closed

Markup is not rendered correctly issues with comments and links #1390

Siegfriedk opened this issue Dec 16, 2019 · 3 comments · Fixed by #1476
Assignees

Comments

@Siegfriedk
Copy link
Contributor

Description:

We have two render issues with the README.md Markdown in kubeapps:

  • <!-- --> will be rendered as plain text in kubeapps
  • Relative Links break inside kubeapps
    • There was already a issue open for the links but its not solved: Add "id" to headings #709 (not sure though what this solved in detail, just wanted to mention it)

Steps to reproduce the issue:

Create README.md which contains:


<!--ts-->
   * [Chart Details](#chart-details)
<!--te-->


# Chart Details

Describe the results you received:

Rendered output:

<!--ts-->
   * [Chart Details](#chart-details)
<!--te-->


# Chart Details

and link #chart-details is broken.

Describe the results you expected:

Rendered output:

   * [Chart Details](#chart-details)

# Chart Details

and link #chart-details works.

Version of Helm, Kubeapps and Kubernetes:

v1.7.2

@andresmgot
Copy link
Contributor

Hi @Siegfriedk,

Thanks for reporting the issue! The library we are using to parse the READMEs is probably ignoring the comments, we would need to check what's happening.

Regarding the relative links, it's true that it should be fixed, does it work for you if the relative link is outside the "block" <!--- .... -->?

@Siegfriedk
Copy link
Contributor Author

The toc is not inside the comment block but i tested it nonetheless. It doesn't make a difference.

@andresmgot
Copy link
Contributor

Hi @Siegfriedk sorry for the late response! Just letting you know that we are addressing your issue at #1476 and that the fix will be available in the next release. Thanks for reporting!

@andresmgot andresmgot self-assigned this Jan 22, 2020
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

Successfully merging a pull request may close this issue.

3 participants