We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As a writer of AsciiDoc files, I want to be able to limit line length overall but exclude lines I can not shorten, e.g. links with long URLs.
Problem: AsciiDoc supports only line comments, not trailing comments (cf. asciidoctor/asciidoctor#991).
Proposal: Support excluding lines (in certain files) if they match a regular expression. Extend the exclude list to support
exclude
Example usage (for this use case):
.ecrc
{ "exclude": [ { "files": ["*.adoc"], "lines": ["^\\s*link:"] } ] }
(not married to the syntax; I'd image one would like to migrate from string elements like "*.lock" to { files: ["*.lock"] } eventually?)
"*.lock"
{ files: ["*.lock"] }
I would have to test w.r.t. performance impact; but since this is a strictly opt-in feature, the trade-off would be the users'.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As a writer of AsciiDoc files, I want to be able to limit line length overall but exclude lines I can not shorten, e.g. links with long URLs.
Problem: AsciiDoc supports only line comments, not trailing comments (cf. asciidoctor/asciidoctor#991).
Proposal: Support excluding lines (in certain files) if they match a regular expression. Extend the
exclude
list to supportExample usage (for this use case):
.ecrc
(not married to the syntax; I'd image one would like to migrate from string elements like
"*.lock"
to{ files: ["*.lock"] }
eventually?)I would have to test w.r.t. performance impact; but since this is a strictly opt-in feature, the trade-off would be the users'.
The text was updated successfully, but these errors were encountered: