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
Anchor tags to reference subsections in the wire specification do not work. When I click on the table of content, say 1. Conventions, the url becomes #/docs/spec/wire?id=1-conventions. The expected url should have _ prepended, #/docs/spec/wire?id=_1-conventions - this can be verified by selecting 1. Conventions from the sidebar.
After some digging, I came across this issue on docsify. When generating the website, docsify added the _ for selectors that start with digits.
What did you want to happen?
Prepending _ for any sections in the table of content that start with a digit will make the link work as expected.
My only concern is that I'm not sure if this would break the expected behavior when markdown-toc is used to generate the table of content. It's not immediately clear to me why markdown-toc was required from reading its official doc.
The text was updated successfully, but these errors were encountered:
What happened?
Anchor tags to reference subsections in the wire specification do not work. When I click on the table of content, say
1. Conventions
, the url becomes#/docs/spec/wire?id=1-conventions
. The expected url should have_
prepended,#/docs/spec/wire?id=_1-conventions
- this can be verified by selecting1. Conventions
from the sidebar.After some digging, I came across this issue on docsify. When generating the website, docsify added the
_
for selectors that start with digits.What did you want to happen?
Prepending
_
for any sections in the table of content that start with a digit will make the link work as expected.My only concern is that I'm not sure if this would break the expected behavior when
markdown-toc
is used to generate the table of content. It's not immediately clear to me whymarkdown-toc
was required from reading its official doc.The text was updated successfully, but these errors were encountered: