-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
Custom marker style #108
Comments
I agree! I've got a number of bug-related issues on my plate before I can consider feature requests, but if you really want you're welcome to open a PR (with tests :D). |
Hi @jez! I'm afraid I won't be able to send a PR – not enough time. I just came across your project and tried it on a small app, but decided not to use it for now. I'm keeping an eye on |
Hi @jez, I'd like to try and implement this feature (pass an argument/flag to |
On my phone right now but npm test should work if I recall correctly.
|
That worked, thanks. Simple enough! On 10 Jun 2016, at 18:52, Jake Zimmerman wrote:
|
The fix for this is on |
I'm linting my
*.md
with remark-linter and one rule I'm checking the files against is that the markers should be*
rather than-
(markdown equally supports both of these options).It would be nice if I could tell doctoc which of the two marker symbols to use in order to avoid linter errors.
The text was updated successfully, but these errors were encountered: