-
Notifications
You must be signed in to change notification settings - Fork 327
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
Add support for Bitbucket Cloud ToC generation #861
Comments
According to #703, Bitbucket doesn't create ids for Markdown headings. Has it changed recently? It would be good if you can provide some links (to some examples). |
Sure, please take a look at this example repository. Bitbucket creates ids for Markdown headers like this: |
Please check out the dev build. |
I have a question about naming: I presumed our convention is And I forgot to tell you that in Lines 381 to 396 in 6f25000
|
Fixed! |
Still missed something. 😂 |
Thank you guys, it is working perfectly now! |
Sorry if I'm asking at the wrong place, but this seemed the best one in my opinion. I'm not understanding how I can enable this feature... I'm currently facing the same issue, where I'd need to prefix Sorry for the somewhat stupid question... Any help is appreciated! |
Please try the dev build: I'm sorry that we're having trouble in releasing a new version. #966 |
Oh, that's why. No problem at all of course! I'll give it a try, thank you. |
Proposal
This would be nice to have ToC slugify option fitted for Bitbucket. On GitHub each link to header looks like
#main-header
, but Bitbucket adds it own prefix on header class, which results in#markdown-header-main-header
.The text was updated successfully, but these errors were encountered: