On that line, both recurse and force are being set to the value of the Force parameter, even though there are separate parameters available for both Recurse and Force. I'm not sure if this was intentional. Just thought i'd mention it.
Since I know about this quirk, I can guess what I should expect (in this case Recurse would be ignored)
Thank you for raising this with us @eehret! While this may seem like a bug, it is actually the intended behavior. @michaeltlombardi could you please call this out in our documentation?
I noticed what, to my eyes, looks like a bug.
https://github.com/Azure/nxtools/blob/main/source/Classes/1.DscResources/01.nxFile.ps1#L384
On that line, both recurse and force are being set to the value of the Force parameter, even though there are separate parameters available for both Recurse and Force. I'm not sure if this was intentional. Just thought i'd mention it.
Since I know about this quirk, I can guess what I should expect (in this case Recurse would be ignored)