-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
Fix broken structure links in documentation #1612
Conversation
boa/src/syntax/lexer/token.rs
Outdated
@@ -108,7 +108,7 @@ pub enum TokenKind { | |||
|
|||
/// A keyword. | |||
/// | |||
/// see: [`Keyword`](../keyword/enum.Keyword.html) | |||
/// see: [`Keyword`](../../ast/keyword/enum.Keyword.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.
Can you check if using directly Keyword
and Punctuator
fixes the links? Because IIRC, if the type is imported it should work.
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.
Actually now that you mention it, it seems that by default rustdoc automatically links the struct inside the enum variant. The additional "see: " is not required".
What I mean is that the green text in the above screenshot already links to the struct. Shall I remove the two explicit links that anyway seem redundant now ?
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.
Yeah, you can remove them
630d091
to
50ec7fa
Compare
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.
Thanks!
Found some broken links to some structures when perusing the documentation of Lexer and Parser.