Automatically escape and unescape constants with semicolon #320
Conversation
This file contains 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
This is a workaround (fix?) for dotnet/roslyn#51692, basically. We lose all content after the first semicolon in constant and metadata values (presumably Git too). Project properties also suffer from this, but merits unifying it with ThisAssembly.Constants to continue to streamline the implementation.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 is a workaround (fix?) for dotnet/roslyn#51692, basically.
We lose all content after the first semicolon in constant and metadata values (presumably Git too).
Project properties also suffer from this, but merits unifying it with ThisAssembly.Constants to continue to streamline the implementation.