-
Notifications
You must be signed in to change notification settings - Fork 48
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
Attribute 'compatible' #141
Comments
GitHub Settings@naokazuterada, today I've encounted some more edge-case headings that required customizing my MarkdownTOC settings:
{
// remove trailing hyphens:
"pattern": "\\-+$",
"replacement": ""
},
{
// reduce consecutive hyphens:
"pattern": "\\-{2,}",
"replacement": "-"
}, Examples of headings that require this patterns:
without the above substitutions, the generated link would be Possibly there might still be some edge-cases lurking in the dark — which only confirms that managing manual settings for all Git services is quite cumbersome, whereas having server configurations is going to make life much easier, especially with package updates fixing any new uncovered incompatiblity edge case. |
@tajmone |
Purpose
Provide end users with easy configuration of configuration for various sites(GitHub, Gitlab, Bitbucket).
How important it is
Current configurations are complex.
Ref: #139 (comment)
Ideal implementation
is shorthand for
Notes
compatibility
should contain not only 'attributes' setting but alsoid_replacements
setting.The text was updated successfully, but these errors were encountered: