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
Recently, we got a filename into an include statement by accident that evaded newdoc's sanitization by using a weird Unicode apostrophe:
include::modules/security/proc_changing-a-user’s-clearance-level-within-the-defined-security-range-in-mls.adoc[leveloffset=+1]
it broke preview links in an MR
The RFE is to consider a limited allowlist of characters to be used in file names that will not clash with subsequent include statements.
The text was updated successfully, but these errors were encountered:
[Marek] Note to self: use string.is_ascii() here
Sorry, something went wrong.
Sanitize more invalid characters in the module ID; #33
49f4ad3
This is now fixed in the 2.10.2 release. The module ID now replaces all non-ASCII characters with dashes.
No branches or pull requests
Recently, we got a filename into an include statement by accident that evaded newdoc's sanitization by using a weird Unicode apostrophe:
include::modules/security/proc_changing-a-user’s-clearance-level-within-the-defined-security-range-in-mls.adoc[leveloffset=+1]
it broke preview links in an MR
The RFE is to consider a limited allowlist of characters to be used in file names that will not clash with subsequent include statements.
The text was updated successfully, but these errors were encountered: