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

Developers can access documentation for all .NET Core/.NET 5 APIs #43849

Open
17 of 23 tasks
Tracked by #44314 ...
carlossanlop opened this issue Oct 26, 2020 · 3 comments
Open
17 of 23 tasks
Tracked by #44314 ...

Developers can access documentation for all .NET Core/.NET 5 APIs #43849

carlossanlop opened this issue Oct 26, 2020 · 3 comments
Assignees
Labels
area-Meta documentation Documentation bug or enhancement, does not impact product or test code Team:Libraries tracking This issue is tracking the completion of other related issues.
Milestone

Comments

@carlossanlop
Copy link
Member

carlossanlop commented Oct 26, 2020

As part of the 7.0 goals, we want to finish documenting APIs that were shipped without triple slash documentation in previous .NET Core versions.

We expect developers to add documentation directly in triple slash comments in source, since it's new documentation. Triple slash are still going to be used for seeding dotnet-api-docs, which is considered the source of truth after going through language review.

Documentation modifications or augmentations are not part of this effort. Those kinds of changes are expected to be done directly in dotnet-api-docs, since that is the source of truth.

We will include APIs from Runtime Libraries (System and Microsoft.Extensions namespaces), WPF and WinForms.

Total undocumented APIs per repo + namespace

Runtime - System
System APIs 1.x 2.x 5.x Total debt
S.Reflection 192 10 202
S.Reflection.PortableExecutable 135   135
S.Reflection.Emit 32 13 45
S.Security.Cryptography.Pkcs   18 18
S.Collections.Immutable 14   14
S.Formats.Cbor 5 5
S.Diagnostics 3 1 4
S.Linq 3   3
S.Security.Cryptography 1 2 3
S.ServiceModel.Channels 3   3
S.ComponentModel 2   2
S.Security.Permissions   2 2
S.Net 1   1
S.Net.Http   1 1
Total 386 47 5 438
Runtime - Microsoft.Extensions
Microsoft.Extensions APIs 1.x 2.x 3.x 5.x Total debt
M.E.DependencyModel       113 113
M.E.Logging.Console 36 6   5 47
M.E.Logging 37 9     46
M.E.Caching.Memory 33 2     35
M.E.Primitives 23 10     33
M.E.DependencyInjection 18 9 1 2 30
M.E.Hosting   19 6   25
M.E.DependencyModel.Resolution       22 22
M.E.Caching.Distributed 16 1 1   18
M.E.DiagnosticAdapter 15 3     18
M.E.Options 4 13   1 18
M.E.Configuration 10 4 2   16
M.E.Logging.Abstractions 5 7   1 13
M.E.Logging.EventLog 12 1     13
M.E.Http.Logging   7   2 9
M.E.Caching.Redis 8       8
M.E.Hosting.Systemd     8   8
M.E.Caching.SqlServer 7       7
M.E.FileSystemGlobbing 7       7
M.E.FileSystemGlobbing.Abstractions 7       7
M.E.Hosting.WindowsServices     6   6
M.E.Http   6     6
M.E.Logging.Debug 5 1     6
M.E.Logging.TraceSource 5       5
M.E.Caching.StackExchangeRedis   4     4
M.E.Configuration.Xml 3   1   4
M.E.FileProviders 4       4
M.E.Configuration.Ini 2   1   3
M.E.Configuration.Json 2   1   3
M.E.Configuration.NewtonsoftJson     3   3
M.E.Logging.Configuration   3     3
M.E.Logging.EventSource     3   3
M.E.Configuration.CommandLine 2       2
M.E.Configuration.EnvironmentVariables 2       2
M.E.Configuration.Memory 2       2
M.E.Configuration.UserSecrets 2       2
M.E.DependencyInjection.Extensions 1 1     2
M.E.DiagnosticAdapter.Infrastructure 1       1
M.E.FileProviders.Composite 1       1
M.E.FileProviders.Physical 1       1
Total 271 106 33 146 556
WinForms
WinForms APIs 3.x 5.x Total debt
System.Windows.Forms   73 73
System.Windows.Diagnostics   9 9
System.Windows.Markup   8 8
System.Windows.Forms.VisualStyles   1 1
Total 0 91 91
WPF
WPF APIs 3.x Total debt
System.Xaml.Permissions 2 2
Total 2 2

Issues tracking debt per area

System

Microsoft.Extensions

WinForms

WPF

@carlossanlop carlossanlop added the documentation Documentation bug or enhancement, does not impact product or test code label Oct 26, 2020
@carlossanlop carlossanlop added this to the 6.0.0 milestone Oct 26, 2020
@reflectronic
Copy link
Contributor

There is a significant amount of missing documentation under System.Reflection.Metadata and System.Reflection.Metadata.Ecma335. I do not see these two namespaces tracked by this issue. I suppose that these APIs are not the most critical (and many of the missing members are simply things like implicit conversions with little to elaborate on), but is the progress being tracked anywhere for these?

@carlossanlop
Copy link
Member Author

carlossanlop commented Oct 27, 2020

I suppose that these APIs are not the most critical

Correct, that is the main reason - These are advanced APIs, so we have not been considering them for documentation efforts.

The other reason is that their API surface is huge. Combined with the first reason, it does not make sense to spend so much time on these advanced APIs.

We made the same decision with System.Runtime.Intrinsics.

We will plan to address them at a later time.

This shouldn't stop user contributions though. If you feel like you have good knowledge on these APIs, feel free to document them.

@danmoseley danmoseley added Bottom Up Work Not part of a theme, epic, or user story User Story A single user-facing feature. Can be grouped under an epic. labels Nov 3, 2020
@danmoseley danmoseley changed the title API documentation debt Developers can access documentation for all .NET Core/.NET 5 APIs Nov 29, 2020
@jeffhandley jeffhandley self-assigned this Dec 17, 2020
@carlossanlop carlossanlop added the Cost:L Work that requires one engineer up to 4 weeks label Jan 14, 2021
@jeffhandley jeffhandley added the Priority:1 Work that is critical for the release, but we could probably ship without label Jan 21, 2021
@jeffhandley jeffhandley added the tracking This issue is tracking the completion of other related issues. label Oct 4, 2021
@jeffhandley jeffhandley modified the milestones: 6.0.0, 7.0.0 Oct 9, 2021
@joperezr joperezr moved this to Needs Consultation in Triage POD for Reflection, META, etc. Nov 2, 2021
@jeffhandley jeffhandley removed the Bottom Up Work Not part of a theme, epic, or user story label Jan 9, 2022
@jeffhandley jeffhandley modified the milestones: 7.0.0, 8.0.0 Aug 11, 2022
@jeffhandley jeffhandley removed the Priority:1 Work that is critical for the release, but we could probably ship without label Oct 22, 2022
@Xyncgas
Copy link

Xyncgas commented Apr 4, 2023

Meanwhile we can share https://source.dot.net with people

@carlossanlop carlossanlop modified the milestones: 8.0.0, 9.0.0 Oct 11, 2023
@jeffhandley jeffhandley removed User Story A single user-facing feature. Can be grouped under an epic. Cost:L Work that requires one engineer up to 4 weeks labels Jul 28, 2024
@jeffhandley jeffhandley modified the milestones: 9.0.0, Future Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Meta documentation Documentation bug or enhancement, does not impact product or test code Team:Libraries tracking This issue is tracking the completion of other related issues.
Projects
No open projects
Status: Needs Consultation
Development

No branches or pull requests

6 participants