Port System.Text.Json triple slash to docs

[carlossanlop]

Found with DocsPortingTool.

Also included a System.Text.RegularExpressions port (by mistake, but let's get it merged). @tannergooding @pgovind

@gewarren I'm targeting the net6-rc1 branch.

[ghost]

Tagging subscribers to this area: @eiriktsarpalis, @layomia
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Found with DocsPortingTool

Author:	carlossanlop
Assignees:	carlossanlop
Labels:	area-System.Text.Json
Milestone:	-

[eiriktsarpalis]

Thanks. This should address the final batch of APIs that were added in RC1.

Fixes dotnet/runtime#54862

[carlossanlop]

Thanks. This should address the final batch of APIs that were added in RC1.

Actually, not yet. There are some more APIs in my report that do not have triple slash. Mostly from System.Text.Json.Nodes.

There's the possibility that the DocsPortingTool is unable to match the DocId of those APIs. Could you help me figure out if it's due to lack of docs or a bug in the tool? @eiriktsarpalis

[pgovind]

LGTM

[eiriktsarpalis]

@carlossanlop shouldn't this also be ported to main?

[carlossanlop]

@eiriktsarpalis no, main is not yet targeting RC1. The latest APIs only exist in the net6-rc1 branch, which is the one we are currently using for the last 6.0 docs, and we will eventually merge that branch into main.

[opbld32]

Docs Build status updates of commit f2f4e78:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.Text.Json.Serialization.Metadata/JsonMetadataServices.xml	✅Succeeded	View
xml/System.Text.Json.Serialization.Metadata/JsonObjectInfoValues`1.xml	✅Succeeded	View
xml/System.Text.Json.Serialization.Metadata/JsonParameterInfoValues.xml	✅Succeeded	View
xml/System.Text.Json.Serialization/JsonConverter`1.xml	✅Succeeded	View
xml/System.Text.Json/JsonSerializer.xml	✅Succeeded	View
xml/System.Text.RegularExpressions/Capture.xml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel