Frode Flaten

Should we close old issues like this as "not planned" to clear backlog?

Not sure if this belongs here, but might add the `about_Pester` help file is very outdated (v3?). E.g. it mentions New-Fixture which is not available atm in Pester v5 (found...

How can we best document the assertion operators? The private functions like `Should-BeOfType` are usually documented, but they are hidden behind the public `Should` which only include a few examples....

I read the mentioned issue and comment as a plan to replace the current comment based help with external markdown files as source and use PlatyPS to create MAML xml...

Still able to repro in 5.3.3. `Get-Command` is lazy-loading the parameters. Can repro with `Set-Alias`, but not built-in aliases as they've probably been called sometime. So `CommandInfo` is passed to...

It looks like PowerShell tries to lazy-load the metadata for the original function when getting it's parameters. When doing that, PowerShell doesn't look in the local scope in the caller...

I think the simple interface looks good, maybe with the mentioned ScriptBlock (+ the current -Container that's not mentioned). The lack of tab-completion and especially validation in string-options in configuration...

IIRC that function isn't called anymore. It's been converted to a c# method in Pester.Factory. Concept probably still applies though.

It's probably `configuration.GetValueOrNull("CoveragePercentTarget")` used in config merging returning null (-> default value) unless you explicitly provide a decimal. This works: ```powershell $Config = New-PesterConfiguration @{ CodeCoverage = @{ CoveragePercentTarget =...

I don't see why -Alias shouldn't be a string-array parameter. String will auto-convert so no breaking change. 🙂 Tagging as feature for now.