You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following APIs were introduced in 6.0 and did not get documented in triple slash. They will need to be manually documented directly in dotnet-api-docs, and must target the net6-rc1 branch. This needs to be done before Tuesday September 14th so we have enough time to generate the IntelliSense package that will be shipped to GA.
@steveharter@layomia could you take a look? We're missing a few doc elements from triple slash documentation. On quick inspection these seem to be minor things such as missing <returns/> or ` elements but these should be added for 6.0.0.
These can be identified by looking for the To be added. placeholder in the linked xml docs. Note that some of these will be fixed by #7094 so I would recommend holding off until that PR is merged.
I generated a Docs Excel report last night. So if I exclude SourceGeneration, this is the list of APIs that need some documentation. The most important ones are those with a missing summary. They should all have that item filled out at the very least:
I noticed several APIs are op_explicit or op_implicit inherited members. Adding the <inheritdoc/> documentation tag was the correct thing to do, but unfortunately the parent APIs are not documented, so nothing can be ported. Since the parent API is not really part of your namespace, I am going to exclude those from the undoc list.
@steveharter@layomia there are still a few that were not covered in the last PR, can you please take care of them? Reminder that today is the last day to merge to the net6-rc1 branch in dotnet-api-docs, before we snap.
Activity
eiriktsarpalis commentedon Jun 29, 2021
Given that we are still working on adding new APIs, this issue should be addressed after STJ is feature complete for 6.0
eiriktsarpalis commentedon Aug 16, 2021
#57302 is adding new APIs to System.Text.Json, likely the final set of changes for 6.0
carlossanlop commentedon Sep 3, 2021
I ported all the documentation that existed in triple slash: dotnet/dotnet-api-docs#7094
I updated the list of undoc APIs that have yet to be documented. See the issue description.
eiriktsarpalis commentedon Sep 6, 2021
@steveharter @layomia could you take a look? We're missing a few doc elements from triple slash documentation. On quick inspection these seem to be minor things such as missing
<returns/>or ` elements but these should be added for 6.0.0.These can be identified by looking for the
To be added.placeholder in the linked xml docs. Note that some of these will be fixed by #7094 so I would recommend holding off until that PR is merged.eerhardt commentedon Sep 7, 2021
Nothing in the "SourceGeneration" namespace is public API that consumers should be using. @carlossanlop - is there a way we can remove any members coming from the https://github.com/dotnet/runtime/blob/main/src/libraries/System.Text.Json/gen/System.Text.Json.SourceGeneration.csproj library? We shouldn't have them on docs.microsoft.com.
carlossanlop commentedon Sep 9, 2021
@eerhardt thanks for letting me know. I'll remove those APIs from the undoc debt. I opened a bug for the Docs dev team to address it.
carlossanlop commentedon Sep 9, 2021
I generated a Docs Excel report last night. So if I exclude SourceGeneration, this is the list of APIs that need some documentation. The most important ones are those with a missing summary. They should all have that item filled out at the very least:
eiriktsarpalis commentedon Sep 13, 2021
@carlossanlop some of the methods marked as missing documentation are actually overrides marked with the
<inheritdoc/>elements, for exampleruntime/src/libraries/System.Text.Json/src/System/Text/Json/Nodes/JsonObject.cs
Lines 84 to 85 in 44996f8
What's best practice in this case? Do we really need to duplicate documentation in this case?
Note that the
System.Text.Json.Metadatanamespace provides runtime APIs for sourcegen, so should be excluded as well.carlossanlop commentedon Sep 13, 2021
@eiriktsarpalis I fixed DocsPortingTool recently to detect the
<inheritdoc/>tag and collect the documentation from the parent API.eiriktsarpalis commentedon Sep 13, 2021
Fixed by dotnet/dotnet-api-docs#7157
carlossanlop commentedon Sep 13, 2021
Thanks, @eiriktsarpalis for the PR!
I noticed several APIs are
op_explicitorop_implicitinherited members. Adding the<inheritdoc/>documentation tag was the correct thing to do, but unfortunately the parent APIs are not documented, so nothing can be ported. Since the parent API is not really part of your namespace, I am going to exclude those from the undoc list.@steveharter @layomia there are still a few that were not covered in the last PR, can you please take care of them? Reminder that today is the last day to merge to the net6-rc1 branch in dotnet-api-docs, before we snap.
eiriktsarpalis commentedon Sep 14, 2021
Fixed in dotnet/dotnet-api-docs#7180