CBOR and platform check API updates #4992
Conversation
|
Docs Build status updates of commit af9c153: ✅ Validation status: passed
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:
|
| @@ -20,7 +20,7 @@ | |||
| </Attribute> | |||
| </Attributes> | |||
| <Docs> | |||
| <summary>To be added.</summary> | |||
| <summary>The exception that is thrown when Concise Binary Object Representation (CBOR) content is invalid.</summary> | |||
There was a problem hiding this comment.
Do we need to do this for every type? It feels redundant since the namespace also contains the acronym. I would suggest expanding it only for the CborWriter and CborReader classes, since they are the entrypoints to this particular API.
| @@ -1,6 +1,6 @@ | |||
| <Namespace Name="System.Formats.Cbor"> | |||
| <Docs> | |||
| <summary>To be added.</summary> | |||
| <summary>Contains types used in reading and writing data in the Concise Binary Object Representation (CBOR) format.</summary> | |||
There was a problem hiding this comment.
@eiriktsarpalis Thanks for reviewing. I removed the spelled out acronym from all but reader and writer, but I also added a namespace summary here. Does this look okay?
There was a problem hiding this comment.
|
Docs Build status updates of commit 59584ba: ✅ Validation status: passed
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:
|
Spell out CBOR acronym on first use.
Update platform check method descriptions.
(Hide whitespace changes in diff.)