Skip to content

Commit

Permalink
Cbor docs - Fix SA1121: Use built-in type alias (#51516)
Browse files Browse the repository at this point in the history
Co-authored-by: carlossanlop <carlossanlop@users.noreply.github.com>
  • Loading branch information
carlossanlop and carlossanlop authored Apr 19, 2021
1 parent dc634cc commit acff8f3
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ public partial class CborReader
/// The next value uses a CBOR encoding that is not valid under the current conformance mode.</exception>
/// <remarks>
/// Map contents are consumed as if they were arrays twice the length of the map's declared size.
/// For instance, a map of size 1 containing a key of type <see cref="System.Int32" /> with a value of type <see cref="System.String" />
/// For instance, a map of size 1 containing a key of type <see cref="int" /> with a value of type <see cref="string" />
/// must be consumed by successive calls to <see cref="ReadInt32" /> and <see cref="ReadTextString" />.
/// It is up to the caller to keep track of whether the next value is a key or a value.
/// Fundamentally, this is a technical restriction stemming from the fact that CBOR allows keys of arbitrary type,
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ public partial class CborWriter
/// In canonical conformance modes, the writer will reject indefinite-length writes unless
/// the <see cref="ConvertIndefiniteLengthEncodings" /> flag is enabled.
/// Map contents are written as if arrays twice the length of the map's declared size.
/// For instance, a map of size 1 containing a key of type <see cref="System.Int32" /> with a value of type string must be written
/// For instance, a map of size 1 containing a key of type <see cref="int" /> with a value of type string must be written
/// by successive calls to <see cref="WriteInt32(int)" /> and <see cref="WriteTextString(System.ReadOnlySpan{char})" />.
/// It is up to the caller to keep track of whether the next call is a key or a value.
/// Fundamentally, this is a technical restriction stemming from the fact that CBOR allows keys of any type,
Expand Down

0 comments on commit acff8f3

Please sign in to comment.