Mocking cmdlet without positional parameters#477
Merged
dlwyatt merged 2 commits intopester:masterfrom Feb 21, 2016
PetSerAl:positional-binding-fix
Merged
Mocking cmdlet without positional parameters#477dlwyatt merged 2 commits intopester:masterfrom PetSerAl:positional-binding-fix
dlwyatt merged 2 commits intopester:masterfrom
PetSerAl:positional-binding-fix
Conversation
Member
|
For the record, I'm impressed! :) The Mocking code is by far the messiest, hardest to follow part of Pester, and you keep finding these little improvements that I'd never even noticed. |
dlwyatt
added a commit
that referenced
this pull request
Feb 21, 2016
Mocking cmdlet without positional parameters
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.
If advanced function does not specify any positional parameters, then PowerShell make all function parameters to be positional implicitly. This is not true for cmdlets. So that, mock of cmdlet can have different parameter binding behavior compared to original cmdlet. In v3+ you can disable implicit positional parameter binding behavior by specifying
PositionalBinding=$falseinCmdletBindingattribute.