Skip to content

Fix ShouldProcess rule #652

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 15, 2016
Merged

Fix ShouldProcess rule #652

merged 3 commits into from
Nov 15, 2016

Conversation

kapilmb
Copy link

@kapilmb kapilmb commented Nov 1, 2016

  • Does not trigger if caller does not support ShouldProcess but calls a built-in cmdlet or function that supports ShouldProcess
  • Triggers if a function calls ShouldProcess but does not support ShouldProcess

Resolves #644
Resolves #646
Resolves #650


This change is Reviewable

Kapil Borle added 3 commits October 26, 2016 17:02
* Flag a function if it calls shouldprocess but supports shouldprocess
* Do not flag a function if it does not support shouldprocess and calls commands that support shouldprocess
@raghushantha
Copy link
Member

:lgtm:


Comments from Reviewable

@raghushantha
Copy link
Member

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@kapilmb kapilmb merged commit 4cda851 into development Nov 15, 2016
@kapilmb
Copy link
Author

kapilmb commented Nov 15, 2016

@raghushantha Thanks!

@kapilmb kapilmb deleted the kapilmb/FixShouldProcess branch November 17, 2016 06:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants