-
Notifications
You must be signed in to change notification settings - Fork 204
Fix tests by adding markdown tags #922
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
base: master
Are you sure you want to change the base?
Conversation
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.
I think if they help with better codeblock hinting (or avoiding trying to use Rust syntax highlighting for non-Rust snippets), it seems fine
So maybe the question is, are we interested in fixing these tests? Are we using tests here anyway?
Note that AFAIK none of these are tests, and are only codeblocks for stylistic/illustrative reasons.
```console | ||
- [`std::ptr::null_mut`](https://doc.rust-lang.org/std/ptr/fn.null_mut.html) | ||
``` |
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.
Nit: this is actually md
or markdown
, right?
@@ -10,7 +10,7 @@ To transfer an issue to another repository, enter a comment with the form: | |||
|
|||
It is recommended to also include a comment explaining why you are transferring. For example: | |||
|
|||
``` |
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.
Nit: this is more like text
?
```console | ||
$ cargo run --bin prioritization-agenda | ||
``` |
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.
Remark: I usually use bash
for these, not that it really matters, I think
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.
bash
(or sh
) gives these wrong highlighting... I would say it should only be used for shell snippets, not command invocations
I would console
(as done here) or text
them
@@ -83,21 +83,21 @@ These types of procedural comments can be left on the issue (it's also good to l | |||
Zulip). See the previous section. To facilitate a machine parsable scanning of the concerns | |||
please use the following syntax to formally register a concern: | |||
|
|||
``` | |||
```console |
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.
Nit: these are probably better as text
, because they're rustbot github comments
(BTW, what does |
MDbook uses Highlight.js and it seems to be just an alias for
|
Yes, that's also my understanding (i.e. cosmetic linting) |
Alright, the changes in this PR seems fine in that case. Just wanted to note that I don't think we're running |
I noticed that we have a command
mdbook test
, I have run it and discovered a massive quantity of linting errors.I did a random visual check and adding the
console
parameter to all these quoted texts does not seems to change anything but fixes the tests.So maybe the question is, are we interested in fixing these tests? Are we using tests here anyway?
thanks for sharing an opinion :)
Note: I left out from this patch some lints failures because they involve Rust code and I suspect it's just not linting
Rendered