This repository has been archived by the owner on Sep 4, 2020. It is now read-only.
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.
New-VesterConfig
needs to ask each Vest what its config value should be named. To do this, I used RegEx. (I like RegEx, but this is true.)To fix #178, I employed my new best friend, PowerShell's AST. Private function
Get-VestConfigValue
now handles this work.New-VesterConfig
has been updated with the changes, andSet-VesterConfigValue
has been updated to no longer expect the$Matches
variable.(.md files will merge in with the other PR)