ErrorAction in advanced functions

It appears built in cmdlets inherit the ErrorAction passed to the containing function. I was hoping to find docs confirming this but was not successful.

Is this behavior by design?

I’ve seen this behavior with all common parameters not only -erroraction. See this 2006 post by Jeff Snover :wink:

Thanks for the confirmation Sam.