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 have some headers that has special characters ('<', '>'). Although the headers are rendered fine, the table of content does not render anything in between those characters.
Start the dev server and check the table of content
Expected behavior
Table of content should render that header as /<context>/status
(Write what you thought would happen.)
Actual Behavior
Table of content renders the header as //status
(Write what happened. Add screenshots, if applicable.)
Reproducible Demo
I think this issue is clearly explained and straight-forward to be able to reproduce. If you still need me to create a separate repo with the issue reproduced, please let me know.
The text was updated successfully, but these errors were encountered:
@endiliey - Thanks a lot for looking into this so quickly. Is there any chance that this bug fix can be released as version 1.9.1? Not sure if there are any other bug fixes that can also be released at the same time. I could really use this particular fix right now.
🐛 Bug Report
I have some headers that has special characters ('<', '>'). Although the headers are rendered fine, the table of content does not render anything in between those characters.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
(Write your steps here:)
Create a doc with header like this
### `/<context>/status`
Start the dev server and check the table of content
Expected behavior
Table of content should render that header as
/<context>/status
(Write what you thought would happen.)
Actual Behavior
Table of content renders the header as
//status
(Write what happened. Add screenshots, if applicable.)
Reproducible Demo
I think this issue is clearly explained and straight-forward to be able to reproduce. If you still need me to create a separate repo with the issue reproduced, please let me know.
The text was updated successfully, but these errors were encountered: