[DO NOT MERGE] Testing remarks without endline separation.

[carlossanlop]

Investigation to support this PR: dotnet/runtime#46716

If we backport the comments to triple slash saving lines of code by removing extra empty lines, would the separation would look fine in MS Docs once those comments are sent back to dotnet-api-docs?

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[carlossanlop]

@maryamariyan this is just a testing PR but the bot was unable to apply a label. Do you know if the bot reads the list of files in the PR to decide? I was expecting it to add the IO.Compression label.

[opbld33]

Docs Build status updates of commit fb12290:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit 441c0b8:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[maryamariyan]

@carlossanlop, if you remember we did not have enough issues labeled so the labeler today only reads the title and description.

Only one issue is labeled as area-System.IO.Compression, (list here), and that one is actually an issue not a PR.

So there would have been no way for it would have predicted for this one right off the bat.

[carlossanlop]

Removing the endlines that surround an -or-` causes MS Docs to show everything into one line. The tool needs to preserve empty lines.

https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.-ctor?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

Reconfirmed. Empty lines need to be preserved.
https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.getmaxcompressedlength?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

@safern@gewarren when the time comes where we have DLLs generated by the runtime build alongside their fully documented intellisense XMLs, we should test feeding them to mdoc and see if it is smart enough to determine that one single endline should be rendered as a full <br /> in MS Docs.

[carlossanlop]

Investigation to support this PR: dotnet/runtime#46716

If we backport the comments to triple slash saving lines of code by removing extra empty lines, would the separation would look fine in MS Docs once those comments are sent back to dotnet-api-docs?

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[carlossanlop]

@maryamariyan this is just a testing PR but the bot was unable to apply a label. Do you know if the bot reads the list of files in the PR to decide? I was expecting it to add the IO.Compression label.

[opbld33]

Docs Build status updates of commit fb12290:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit 441c0b8:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[maryamariyan]

@carlossanlop, if you remember we did not have enough issues labeled so the labeler today only reads the title and description.

Only one issue is labeled as area-System.IO.Compression, (list here), and that one is actually an issue not a PR.

So there would have been no way for it would have predicted for this one right off the bat.

[carlossanlop]

Removing the endlines that surround an -or-` causes MS Docs to show everything into one line. The tool needs to preserve empty lines.

https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.-ctor?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

Reconfirmed. Empty lines need to be preserved.
https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.getmaxcompressedlength?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

@safern@gewarren when the time comes where we have DLLs generated by the runtime build alongside their fully documented intellisense XMLs, we should test feeding them to mdoc and see if it is smart enough to determine that one single endline should be rendered as a full <br /> in MS Docs.

[carlossanlop]

Investigation to support this PR: dotnet/runtime#46716

If we backport the comments to triple slash saving lines of code by removing extra empty lines, would the separation would look fine in MS Docs once those comments are sent back to dotnet-api-docs?

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[carlossanlop]

@maryamariyan this is just a testing PR but the bot was unable to apply a label. Do you know if the bot reads the list of files in the PR to decide? I was expecting it to add the IO.Compression label.

[opbld33]

Docs Build status updates of commit fb12290:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit 441c0b8:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[maryamariyan]

@carlossanlop, if you remember we did not have enough issues labeled so the labeler today only reads the title and description.

Only one issue is labeled as area-System.IO.Compression, (list here), and that one is actually an issue not a PR.

So there would have been no way for it would have predicted for this one right off the bat.

[carlossanlop]

Removing the endlines that surround an -or-` causes MS Docs to show everything into one line. The tool needs to preserve empty lines.

https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.-ctor?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

Reconfirmed. Empty lines need to be preserved.
https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.getmaxcompressedlength?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

@safern@gewarren when the time comes where we have DLLs generated by the runtime build alongside their fully documented intellisense XMLs, we should test feeding them to mdoc and see if it is smart enough to determine that one single endline should be rendered as a full <br /> in MS Docs.

[carlossanlop]

Investigation to support this PR: dotnet/runtime#46716

If we backport the comments to triple slash saving lines of code by removing extra empty lines, would the separation would look fine in MS Docs once those comments are sent back to dotnet-api-docs?

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[carlossanlop]

@maryamariyan this is just a testing PR but the bot was unable to apply a label. Do you know if the bot reads the list of files in the PR to decide? I was expecting it to add the IO.Compression label.

[opbld33]

Docs Build status updates of commit fb12290:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit 441c0b8:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[maryamariyan]

@carlossanlop, if you remember we did not have enough issues labeled so the labeler today only reads the title and description.

Only one issue is labeled as area-System.IO.Compression, (list here), and that one is actually an issue not a PR.

So there would have been no way for it would have predicted for this one right off the bat.

[carlossanlop]

Removing the endlines that surround an -or-` causes MS Docs to show everything into one line. The tool needs to preserve empty lines.

https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.-ctor?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

Reconfirmed. Empty lines need to be preserved.
https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.getmaxcompressedlength?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

@safern@gewarren when the time comes where we have DLLs generated by the runtime build alongside their fully documented intellisense XMLs, we should test feeding them to mdoc and see if it is smart enough to determine that one single endline should be rendered as a full <br /> in MS Docs.

[carlossanlop]

Investigation to support this PR: dotnet/runtime#46716

If we backport the comments to triple slash saving lines of code by removing extra empty lines, would the separation would look fine in MS Docs once those comments are sent back to dotnet-api-docs?

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[carlossanlop]

@maryamariyan this is just a testing PR but the bot was unable to apply a label. Do you know if the bot reads the list of files in the PR to decide? I was expecting it to add the IO.Compression label.

[opbld33]

Docs Build status updates of commit fb12290:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit 441c0b8:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[maryamariyan]

@carlossanlop, if you remember we did not have enough issues labeled so the labeler today only reads the title and description.

Only one issue is labeled as area-System.IO.Compression, (list here), and that one is actually an issue not a PR.

So there would have been no way for it would have predicted for this one right off the bat.

[carlossanlop]

Removing the endlines that surround an -or-` causes MS Docs to show everything into one line. The tool needs to preserve empty lines.

https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.-ctor?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

Reconfirmed. Empty lines need to be preserved.
https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.getmaxcompressedlength?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

@safern@gewarren when the time comes where we have DLLs generated by the runtime build alongside their fully documented intellisense XMLs, we should test feeding them to mdoc and see if it is smart enough to determine that one single endline should be rendered as a full <br /> in MS Docs.

[carlossanlop]

Investigation to support this PR: dotnet/runtime#46716

If we backport the comments to triple slash saving lines of code by removing extra empty lines, would the separation would look fine in MS Docs once those comments are sent back to dotnet-api-docs?

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[carlossanlop]

@maryamariyan this is just a testing PR but the bot was unable to apply a label. Do you know if the bot reads the list of files in the PR to decide? I was expecting it to add the IO.Compression label.

[opbld33]

Docs Build status updates of commit fb12290:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit 441c0b8:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[maryamariyan]

@carlossanlop, if you remember we did not have enough issues labeled so the labeler today only reads the title and description.

Only one issue is labeled as area-System.IO.Compression, (list here), and that one is actually an issue not a PR.

So there would have been no way for it would have predicted for this one right off the bat.

[carlossanlop]

Removing the endlines that surround an -or-` causes MS Docs to show everything into one line. The tool needs to preserve empty lines.

https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.-ctor?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

Reconfirmed. Empty lines need to be preserved.
https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.getmaxcompressedlength?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

@safern@gewarren when the time comes where we have DLLs generated by the runtime build alongside their fully documented intellisense XMLs, we should test feeding them to mdoc and see if it is smart enough to determine that one single endline should be rendered as a full <br /> in MS Docs.

[carlossanlop]

Investigation to support this PR: dotnet/runtime#46716

If we backport the comments to triple slash saving lines of code by removing extra empty lines, would the separation would look fine in MS Docs once those comments are sent back to dotnet-api-docs?

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[carlossanlop]

@maryamariyan this is just a testing PR but the bot was unable to apply a label. Do you know if the bot reads the list of files in the PR to decide? I was expecting it to add the IO.Compression label.

[opbld33]

Docs Build status updates of commit fb12290:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit 441c0b8:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[maryamariyan]

@carlossanlop, if you remember we did not have enough issues labeled so the labeler today only reads the title and description.

Only one issue is labeled as area-System.IO.Compression, (list here), and that one is actually an issue not a PR.

So there would have been no way for it would have predicted for this one right off the bat.

[carlossanlop]

Removing the endlines that surround an -or-` causes MS Docs to show everything into one line. The tool needs to preserve empty lines.

https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.-ctor?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

Reconfirmed. Empty lines need to be preserved.
https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.getmaxcompressedlength?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

@safern@gewarren when the time comes where we have DLLs generated by the runtime build alongside their fully documented intellisense XMLs, we should test feeding them to mdoc and see if it is smart enough to determine that one single endline should be rendered as a full <br /> in MS Docs.

[carlossanlop]

Investigation to support this PR: dotnet/runtime#46716

If we backport the comments to triple slash saving lines of code by removing extra empty lines, would the separation would look fine in MS Docs once those comments are sent back to dotnet-api-docs?

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[carlossanlop]

@maryamariyan this is just a testing PR but the bot was unable to apply a label. Do you know if the bot reads the list of files in the PR to decide? I was expecting it to add the IO.Compression label.

[opbld33]

Docs Build status updates of commit fb12290:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit 441c0b8:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.IO.Compression/BrotliEncoder.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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[maryamariyan]

@carlossanlop, if you remember we did not have enough issues labeled so the labeler today only reads the title and description.

Only one issue is labeled as area-System.IO.Compression, (list here), and that one is actually an issue not a PR.

So there would have been no way for it would have predicted for this one right off the bat.

[carlossanlop]

Removing the endlines that surround an -or-` causes MS Docs to show everything into one line. The tool needs to preserve empty lines.

https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.-ctor?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

Reconfirmed. Empty lines need to be preserved.
https://review.docs.microsoft.com/en-us/dotnet/api/system.io.compression.brotliencoder.getmaxcompressedlength?view=net-5.0&branch=pr-en-us-5213

[carlossanlop]

@safern@gewarren when the time comes where we have DLLs generated by the runtime build alongside their fully documented intellisense XMLs, we should test feeding them to mdoc and see if it is smart enough to determine that one single endline should be rendered as a full <br /> in MS Docs.