-
Notifications
You must be signed in to change notification settings - Fork 35
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
chore(docs): upgrade to Docusaurus v3 #1558
Conversation
Deploying hydroflow with Cloudflare Pages
|
6ac04d5
to
45187dc
Compare
if (grammar == rustLanguage) { | ||
text = text.split("\n").filter(line => !line.startsWith("# ")).join("\n"); | ||
PrismObject.hooks.add("after-tokenize", function(env) { | ||
if (env.language == "rust") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be === Prism.languages.rust
? (should at least be triple equal for style)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not in this case, it's just a string identifier rather than an object.
"{}", | ||
read_string | ||
.split("<!--") | ||
.map(|t| t.replace("<", "\\<")) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
\\<
not <
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Either works, picked \\
to minimize the difference from the previously generated docs.
Main breaking change is MDX parsing, which trips up on unescaped `<` in the generated docs, so we have to adjust the generator logic.
Main breaking change is MDX parsing, which trips up on unescaped
<
in the generated docs, so we have to adjust the generator logic.