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

Reconcile dotnet-api-docs descriptions with dotnet/runtime /// #35596

Open
gewarren opened this issue Jun 2, 2023 · 0 comments
Open

Reconcile dotnet-api-docs descriptions with dotnet/runtime /// #35596

gewarren opened this issue Jun 2, 2023 · 0 comments
Assignees
Labels
doc-enhancement Improve the current content [org][type][category] Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest.

Comments

@gewarren
Copy link
Contributor

gewarren commented Jun 2, 2023

  1. Generate IntelliSense XML files for each namespace in dotnet/runtime (see instructions below) - use a specific tag so all APIs already exist in dotnet-api-docs.
  2. Copy the IntelliSense XML files to a branch in the binaries repo.
  3. Consider (temporarily) reformatting all the ECMAXML files if this generates less noise in the IntelliSense files.
    • CLI: find . -name "*.xml" -type f | xargs -I'{}' xmllint --output '{}' --format '{}' (but this tool might do unwanted things)
    • VS Code extension (Red Hat XML) with xml.format.maxlinewidth set to 0 (disable) - sample PR is here.
  4. Use the doc comment resolver tool in dotnet/docs-tools to update the IntelliSense files with any conflicting text from the dotnet-api-docs repo.
  5. Open each file that was modified and resolve all the conflicts.
  6. Run the CI pipeline to import the doc comments.
  7. Use https://github.com/dotnet/api-docs-sync/tree/main/src/PortToTripleSlash to port the comments back to ///.
  8. Open PRs in the dotnet/runtime repo.

Related items:

dotnet/runtime#44969
User Story 633174: [.NET] Partially import doc comments - Boards (azure.com)


Associated WorkItem - 97017

@gewarren gewarren self-assigned this Jun 2, 2023
@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Jun 2, 2023
@gewarren gewarren added Pri1 High priority, do before Pri2 and Pri3 doc-enhancement Improve the current content [org][type][category] 🗺️ reQUEST Triggers an issue to be imported into Quest. and removed ⌚ Not Triaged Not triaged Pri3 labels Jun 2, 2023
@github-actions github-actions bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Jun 3, 2023
@gewarren gewarren changed the title Synchronize dotnet-api-docs descriptions to dotnet/runtime /// Renconcile dotnet-api-docs descriptions with dotnet/runtime /// Dec 7, 2023
@gewarren gewarren changed the title Renconcile dotnet-api-docs descriptions with dotnet/runtime /// Reconcile dotnet-api-docs descriptions with dotnet/runtime /// Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-enhancement Improve the current content [org][type][category] Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest.
Projects
No open projects
Status: Slipped
Status: Slipped
Status: Slipped
Status: Slipped
Development

No branches or pull requests

2 participants