Skip to content
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.

CloudBlobClient.GetRootContainerReference XmlDoc is not correctly formatted #928

Closed
Chris-Johnston opened this issue Aug 27, 2019 · 1 comment · May be fixed by #941
Closed

CloudBlobClient.GetRootContainerReference XmlDoc is not correctly formatted #928

Chris-Johnston opened this issue Aug 27, 2019 · 1 comment · May be fixed by #941
Labels

Comments

@Chris-Johnston
Copy link

/// <remarks>Note that the root container must be explicitly created, if it does not already exist, before
/// you can read from it or write to it.</remarks>

The formatting of the Remarks field for this method appears to be incorrectly formatted, as seen in the docs. Maybe the xmldoc comments don't like the newline? I haven't seen this issue before myself.

Chris-Johnston added a commit to Chris-Johnston/azure-storage-net that referenced this issue Oct 4, 2019
This change fixes the formatting of the `<remarks>` field of the xmldoc for CloudBlobClient.GetRootContainerReference. It appears fine when reading the source code, but on docs.microsoft.com, the second line appears indented. I think this may be because of the newline in this block.
This newline in this block has been removed. There are other LOC in this file that are around or above the character count per line, if keeping a consistent ruler is an issue.
Chris-Johnston added a commit to Chris-Johnston/azure-storage-net that referenced this issue Oct 4, 2019
This change fixes the formatting of the `<remarks>` field of the xmldoc for CloudBlobClient.GetRootContainerReference. It appears fine when reading the source code, but on docs.microsoft.com, the second line appears indented. I think this may be because of the newline in this block.
This newline in this block has been removed. There are other LOC in this file that are around or above the character count per line, if keeping a consistent ruler is an issue.
@seanmcc-msft
Copy link
Member

We'll fix this in a future release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants