Collection selector about powershelltraps HOT 3 CLOSED

Yes, this should be in the list. I have been trapped by this feature, too. Not even because of typos. E.g. I expect a variable $x to be a scalar with some property Prop and I check this property as $x.Prop -eq 42. If something goes not as expected $x may be a collection instead of expected scalar. In this case in v2 $x.Prop -eq 42 gives either false or error in the strict mode. In v3 $x.Prop is a collection of values, one of them is 42, so my check gives true as if all is "fine". But I did not expect $x to be a collection. I.e. v2 helps me to reveal some unexpected issues earlier. v3 rather hides them at this point.

from powershelltraps.

For my use case at least there is a workaround. The check should be done as 42 -eq $x.Prop. Then it will not be evaluated to true if $x is a collection.

from powershelltraps.

Pushed as Collection-property-enumeration. Please close the issue if it looks good.

Later on I am going to add one more test case which shows how the typical "unexpected output" trap is combined with this one.

from powershelltraps.