-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Update docs for PipeReader.TryRead #52237
Merged
jeffhandley
merged 5 commits into
dotnet:main
from
waf:update-docs-for-streampipereader-tryread
Oct 21, 2021
+9
−1
Merged
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
855ff2e
Update docs for PipeReader.TryRead
waf 8ca456b
remove doc reference to internal StreamPipeReader
waf ecc247c
Merge branch 'main' into update-docs-for-streampipereader-tryread
jeffhandley e61099b
Format remarks as markdown and use !IMPORTANT
jeffhandley 8ac322c
Merge branch 'main' into update-docs-for-streampipereader-tryread
jeffhandley File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@dotnet/docs do we need to quote this and add a
[!NOTE]
for this to show up correctly?I think so looking at this
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 don't know that you can use
[!NOTE]
because that's markdown. /// comments are HTML. I believe the only way to use markdown and the ms.docs syntax extensions (which[!NOTE]
is) is to migrate this content to the external XML API files.Tagging @BillWagner @gewarren for comment.
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.
You'll need to wrap it in
<format>
tags like this:runtime/src/libraries/System.IO.Pipelines/src/System/IO/Pipelines/PipeWriter.cs
Line 46 in 57bfe47
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 updated the comment to use markdown and to use
[!IMPORTANT]
within the remarks. There were no uses of[!NOTE]
anywhere else, but there were a couple other uses of[!IMPORTANT]
within the Pipelines XML docs, so I followed that precedent.