Share InvalidPathChars between PathUtility and RelativePath. #2613
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 necessary to avoid genarting filenames that are treated as invalid by RelativePath on Linux.
surban
requested review from
928PJY,
herohua,
superyyrrzz,
vicancy and
vwxyzh
as code owners
vicancy
approved these changes
Apr 18, 2018
herohua
approved these changes
May 3, 2018
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.
InvalidChars was inconsistent between PathUtility.cs and RelativePath.cs.
This caused DocFx to generate filenames on Linux that were treated as invalid by RelativePath.cs. For example for operator
(*)a filename containing a*was generated, but then rejected by RelativePath resulting in an exception.