-
Notifications
You must be signed in to change notification settings - Fork 519
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
Import our existing documentation from xamarin/apple-api-docs as triple-slash documentation. #17399
Labels
documentation
The issue or pull request is about documentation
dotnet
An issue or pull request related to .NET (6)
Milestone
Comments
rolfbjarne
added a commit
to rolfbjarne/xamarin-macios
that referenced
this issue
May 31, 2024
Import all the xml documentation for types from https://github.com/xamarin/apple-api-docs. Some of this documentation should probably be rewritten, and potentially moved to conceptual documentation, in particular those that contain images (because images can't be imported into xml documentation). The xml documentation for members will come in a later PR. Partial fix for dotnet#17399.
rolfbjarne
added a commit
that referenced
this issue
Jun 6, 2024
Import all the xml documentation for types from https://github.com/xamarin/apple-api-docs. Some of this documentation should probably be rewritten, and potentially moved to conceptual documentation, in particular those that contain images (because images can't be imported into xml documentation). Note that the documentation hasn't been modified in any way; that's not the purpose of this PR. If documentation should be modified for whatever reason, it can be done in a later PR. The xml documentation for members will come in a later PR. Partial fix for #17399.
rolfbjarne
added a commit
that referenced
this issue
Feb 24, 2025
This has to be done in parts, because the Roslyn importer runs out of memory otherwise. Which also means I have no idea how many parts there will end up being. Partial fix for #17399.
rolfbjarne
added a commit
that referenced
this issue
Feb 24, 2025
This has to be done in parts, because the Roslyn importer runs out of memory otherwise. Which also means I have no idea how many parts there will end up being. Partial fix for #17399.
rolfbjarne
added a commit
that referenced
this issue
Feb 26, 2025
This has to be done in parts, because the Roslyn importer runs out of memory otherwise. Which also means I have no idea how many parts there will end up being. Partial fix for #17399.
rolfbjarne
added a commit
that referenced
this issue
Feb 28, 2025
This has to be done in parts, because the Roslyn importer runs out of memory otherwise. Which also means I have no idea how many parts there will end up being. Partial fix for #17399.
rolfbjarne
added a commit
that referenced
this issue
Mar 5, 2025
This has to be done in parts, because the Roslyn importer runs out of memory otherwise. Which also means I have no idea how many parts there will end up being. Partial fix for #17399.
rolfbjarne
added a commit
that referenced
this issue
Mar 6, 2025
This has to be done in parts, because the Roslyn importer runs out of memory otherwise. Which also means I have no idea how many parts there will end up being. Partial fix for #17399.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
The issue or pull request is about documentation
dotnet
An issue or pull request related to .NET (6)
Ref #14372, step 5.
Write a tool (or augment an existing one) that takes the xamarin/apple-api-docs repository as input, figures out where the corresponding API is located (in our source code), and adds a triple-slash comment to the source code.
This is to be done in two steps:
Possible starting points for the tool:
The tool would have to use Roslyn to query and edit our source code.
We might be able to add short and simple API documentation as complete triple-slash comments, but longer should use the feature to reference an external file.
Todos:
The text was updated successfully, but these errors were encountered: