It is already possible to generate a TOC for hashnode using bitdowntoc, by set the anchor prefix option to heading- and using the gitlab preset. However, there is one tiny problem, and this happens when the title starts or ends with special characters. In this case, gitlab keeps a leading or trailing -, while hashnode doesn't. You can try with the heading (title) to see it for yourself.
This issue entails:
adding a new hashnode profile: this may require a specific algorithm or a new option to strip leading/trailing dashes,
testing it manually to find other possible problems,
adding the necessary unit tests
Updating the website page and the documentation can be done here or in another PR. I am available for any doubts or question if you need more information or advice.
It is already possible to generate a TOC for hashnode using bitdowntoc, by set the anchor prefix option to
heading-and using the gitlab preset. However, there is one tiny problem, and this happens when the title starts or ends with special characters. In this case, gitlab keeps a leading or trailing-, while hashnode doesn't. You can try with the heading(title)to see it for yourself.This issue entails:
Updating the website page and the documentation can be done here or in another PR. I am available for any doubts or question if you need more information or advice.