Repository navigation
Add xref links - #867
Add xref links#867
Conversation
|
Next Turn (@NextTurn) : Thanks for your contribution! The author, @, has been notified to review your proposed change. |
|
Hi @corob-msft - Could you review the proposed changes? Thanks. |
Colin Robertson (colin-home)
left a comment
There was a problem hiding this comment.
Next Turn (@NextTurn) - Thanks for taking a look at this and adding a useful enhancement with the xrefs.
Unfortunately, there's a bit of a conflict in styles with the other changes here. While it hasn't been applied consistently across the repo, the formatting policy for language keywords is to use bold when they appear alone or in simple combinations like these, and only to use the inline code style when they appear as part of an expression. Function names have been very inconsistently formatted; we usually use inline code, except in the CRT documentation, where it's practically all bold. Because of some unfortunate CSS choices, the inline code formatting makes some of our pages look like they've been hit by a shotgun. It's not good.
Another policy that's being enforced by some tooling is to use a particular set phrase, "For more information, see [link friendly name](some-link-target)" when making a reference such as the compiler option link. This isn't worth revisiting lots of old topics for, but we'll update things if we're making changes in a topic anyway.
|
@corob-msft - can you provide specific guidance for this PR.
Thanks! |
|
Jak Koke (@Jak-MS) Isn't a review status of "requested changes" sufficiently indicative? #hold-off |
|
@corob-msft - thank you. |
|
Next Turn (@NextTurn) : Thanks for your contribution! The author, @, has been notified to review your proposed change. |
|
Thanks for clarification. |
Pull the compiler option reference out of the table.
|
@corob-msft : Thanks for your contribution! The author, @, has been notified to review your proposed change. |
No description provided.