More robust Path testing in Select-UnitySetupInstance - #206
Merged
Josh Wittner (jwittner) merged 1 commit intoMay 21, 2020
Merged
Conversation
Derek (derekfreed)
left a comment
Member
There was a problem hiding this comment.
Looks like a good change using the Begin statement to check the path!
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 allows the paths to be different cases and use different folder separators. It also safely handles null being passed.
This change fixes Test-UnitySetupInstance, which would previously report 'false' if a Path wasn't specified.