Skip to content

Port System.Diagnostics source code comments to Docs #2336

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

Merged
merged 22 commits into from
Jun 7, 2019

Conversation

carlossanlop
Copy link
Contributor

Summary

Automatically ported triple slash source code comments found in System.Diagnostics that did not exist in dotnet-api-docs.

Fixes #Issue_Number (if available)

@carlossanlop
Copy link
Contributor Author

@mairaw @rpetrusha please take a look.

Adding area owners @wtgodbe, @krwq. Please take a look too, the comments had weird wording, I tried to fix as much as possible but I think it still would need some tweaking.

Updated a multiline comment based on Will's suggestion.
Suggested changes by wtgodbe.
Removed newline.
Removed new lines.
Newlines and link to Write API.
@mairaw mairaw added this to the April 2019 milestone Apr 26, 2019
@mairaw mairaw added the new-content Indicates PRs that contain new articles label Apr 26, 2019
rpetrusha suggestions

Co-Authored-By: Ron Petrusha <ronpet@microsoft.com>
@mairaw
Copy link
Contributor

mairaw commented May 13, 2019

There are still some very long descriptions for some parameters and summaries.

@carlossanlop
Copy link
Contributor Author

@mairaw @rpetrusha done! Sorry for the delay. The last suggestions were larger and required me to edit the files directly in my machine.

@carlossanlop
Copy link
Contributor Author

@rpetrusha let me know if you have any additional comments. Otherwise, we may be able to get this merged.

Copy link

@rpetrusha rpetrusha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, @carlossanlop; I neglected to review the documentation for the last type. I've done that here, and also submitted a commit that corrects some broken xrefs.

Suggestions by rpetrusha.

Co-Authored-By: Ron Petrusha <ronpet@microsoft.com>
@carlossanlop
Copy link
Contributor Author

Sorry, @carlossanlop; I neglected to review the documentation for the last type. I've done that here, and also submitted a commit that corrects some broken xrefs.

No worries, thank you for finding those broken xrefs. I also found one in a remark suggestion. Aside from that one, I commited all your suggestions right away.

Once the build passes, I think we can merge this.

@carlossanlop
Copy link
Contributor Author

@mairaw @rpetrusha I think this one's ready to merge. Maira's requested changes were addressed some time ago, but I'm not sure why the "Changes requested" state has the red icon saying that I have not addressed them. Can you please take a look?

@rpetrusha
Copy link

I was going to dismiss your review because you were on vacation once the build completed, @mairaw, but I completely forgot. Do you want to approve the PR now?

@carlossanlop
Copy link
Contributor Author

Friendly ping @mairaw @rpetrusha

@mairaw
Copy link
Contributor

mairaw commented Jun 6, 2019

Looking at this now.

Copy link
Contributor

@mairaw mairaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made some changes now so I think this is ready to go as long as builds are green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-content Indicates PRs that contain new articles
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants