Skip to content
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

Add some xml comments #88433

Merged
merged 9 commits into from
Jul 11, 2023
Merged

Add some xml comments #88433

merged 9 commits into from
Jul 11, 2023

Conversation

danmoseley
Copy link
Member

Mostly with regex, then I ended up replacing the text with what's in the docs so they can sync one day.

There are still ~100 more files with the old style comments (and many more that don't have XML comments that match the docs) .. perhaps someone in the community is interested in doing more.

@ghost ghost assigned danmoseley Jul 5, 2023
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jul 5, 2023
@teo-tsirpanis teo-tsirpanis added area-Meta and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Jul 5, 2023
@ghost
Copy link

ghost commented Jul 5, 2023

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

Mostly with regex, then I ended up replacing the text with what's in the docs so they can sync one day.

There are still ~100 more files with the old style comments (and many more that don't have XML comments that match the docs) .. perhaps someone in the community is interested in doing more.

Author: danmoseley
Assignees: danmoseley
Labels:

area-Meta

Milestone: -

@danmoseley
Copy link
Member Author

OK, done most of the rest. (Not sure why.)

@danmoseley
Copy link
Member Author

@carlossanlop would you perhaps have a few mins to sign off?

what is the state of your tool/script for porting doc comments into sources? are there working instructions? perhaps I could push this a long a bit at a time in corelib, during coffee breaks so to speak, and do whatever manual fixups as we go. In a few cases the code comment may be better, but I'm guessing that's not many. then we'd slowly be progressing towards sources as doc sourceoftruth.

Copy link
Member

@carlossanlop carlossanlop left a comment

Choose a reason for hiding this comment

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

Thanks for tagging me @danmoseley . Left a bunch of suggestions for you to consider.

The backporting tool (dotnet-api-docs to runtime) isn't fully working yet, but the other one is (runtime to dotnet-api-docs).

@danmoseley
Copy link
Member Author

I'm most interested in this direction. I'd be happy to try a flaky/partial tool if you like, worst case I can't use the results.

danmoseley and others added 5 commits July 10, 2023 15:28
@danmoseley
Copy link
Member Author

all feedback addressed

@ghost ghost locked as resolved and limited conversation to collaborators Aug 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants