Repository navigation
Add Where-Object -Not support #3529
Copy link
Copy link
Closed
Labels
Issue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifIssue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.The issue is fixed.Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Cmdletsgeneral cmdlet issuesgeneral cmdlet issues
Description
Activity
- addedWG-Languageparser, language semanticsparser, language semanticsIssue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassif
on Apr 11, 2017 - added and removedWG-Languageparser, language semanticsparser, language semantics
on Apr 11, 2017 This is an issue with the Where-Object cmdlet not the language itself.
- addedIssue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugUp-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributors
on Apr 12, 2017 Bruce Payette (@BrucePay) Thanks! Clear.
We have related Issue #2658 Do we want to really do this?SimonWahlin commented
on Mar 8, 2018 ContributorMore actionsI think I could add a -Not parameterset to Where-Object.
I can't find any tests for Where-Object, where are those?
powercode commented
on Mar 8, 2018 CollaboratorMore actionsI think it is a good idea.
Simon Wåhlin (@SimonWahlin) I dont found
Where-Objecttest.
I think we should place it intest\powershell\Modules\Microsoft.PowerShell.Corefolder.SimonWahlin commented
on Mar 12, 2018 ContributorMore actionsThanks, I'll try to come up with a set of tests and place them there.
Reacted by IlyaSimon Wåhlin (@SimonWahlin) Please use new Pester 4 syntax in tests.
SimonWahlin commented
on Mar 12, 2018 ContributorMore actionsAbsolutely!
- addedWG-Cmdletsgeneral cmdlet issuesgeneral cmdlet issuesand removed
on Jul 17, 2026
Metadata
Metadata
Assignees
Labels
Issue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifIssue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.The issue is fixed.Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Cmdletsgeneral cmdlet issuesgeneral cmdlet issues
I often have the need to filter for objects that do not have a property specified or who have a falsey value for a property by doing something like the following:
If I am doing the opposite test I can avoid using a script block with Where-Object:
I would like to be able to also avoid using a script block when using -Not which would enable the following: