237dmitry

> Check the link in the first comment of the thread to picture what I would like to have. I think there is no such functionality in micro.

The help output is identical for both functions: ``` -Person Required? true Position? 0 Accept pipeline input? true (ByValue) Parameter set name (All) Aliases Subject Dynamic? false Accept wildcard characters?...

This is because the parameters must be in the parameter set in which they are specified. As you can see, `Parent` is not in the list of available options: ```powershell...

> but the point is that it is a bug: there is no conceivable reason not to allow the combination of `-LiteralPath` with either `-Parent` or `-Leaf` They are incompatible...

> Any bug can be considered "design" No, because with proper syntax you won't get error.

> argue that - With proper syntax there are no errors. - This is not a bug because you should read the docs & mans. Ask the developers why they...

> In my opinion this is rather a feature request. >> so whether there was design intent is ultimately irrelevant - unless someon can come up with a good rationale...

> Cmdlets should be intuitive to use. When there is no technical reason why a given parameter should not work in a specific parameterset, then adding it to the parameterset...

> If you've had a change of heart: great. No, I had not change my position: - this is not a bug, the error is the result of incorrect user...

> So I think no matter how one defines "bug", we're good here. You can think as you want, this is your personal deal.