Clarify raw string literal multi-line rules for opening quotes and whitespace handling #47728
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dotnet-policy-service
bot
added
the
okr-quality
…itespace handling Co-authored-by: BillWagner <[email protected]>
Copilot
AI
changed the title
[WIP] Clarifications regarding two of the listed string literal rules
Clarify raw string literal multi-line rules for opening quotes and whitespace handling
Aug 4, 2025
Copilot finished work on behalf of
BillWagner
August 4, 2025 20:16
BillWagner
approved these changes
Aug 5, 2025
gewarren
approved these changes
Aug 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR clarifies the documentation for multi-line raw string literal rules to address confusion about what "on their own line" means and how whitespace is handled.
Changes Made
Clarified opening/closing quote requirements: Changed "last non-comment token on its respective line" to "last non-whitespace characters on their line" to be more precise and eliminate confusion about whether quotes can appear on the same line as variable declarations.
Improved whitespace handling description: Changed "Whitespace following the opening quote" to "Any whitespace following the opening quotes" for consistency and clarity.
Made plural forms consistent: Changed "closing quote" to "closing quotes" to match the plural form used elsewhere in the documentation.
Issue Addressed
The original documentation caused confusion because:
var xml = """counted as quotes being "on their own line"Example
The existing code example demonstrates the clarified behavior:
In this example:
"""are the last non-whitespace characters on their line (after the variable assignment)Fixes #34192.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.
Internal previews