Not currently using it, but I have been toying around with the idea of snapshot testing in Pester tests for a while... If I were to come up with a PowerShell way to use Verify, would you be interested in contributions to the docs or something like that?
Cool, thanks, approved your PRs to run, so should automatically be triggered, out traveling, but I'll take a quick look, and deeper if needed when back at a keyboard.
Cool, found loads of free time? 😎 Both interns and myself away from the keyboard for Easter, so probably some other project in more need/responsive for feedback.
BTW is there a specific reason Verify.Http dropped net8.0, maintenance burden? Using new features?
it leverages the Microsoft.Net.Http.Headers nuget which dropped support for net8. if u need net8 support i can take a look at how difficult it would be to continue supporting it
Comments
If you want to take a look, it’s all here: https://github.com/purview-dev/purview-telemetry-sourcegenerator
would you accept a pr that removes some of the redundant characters from the path?
But all my Windows PCs have the character limit removed…
I’m honestly not sure why the default limit is still in place, especially for dev pcs.
https://fswb-documentation.knowis.net/4.1/troubleshooting/windows-git-filename-too-long.html
Good find!
I’m back next week, so I’ll check those PRs out then. Thanks!
https://github.com/WCOMAB/AZDOI
BTW is there a specific reason Verify.Http dropped net8.0, maintenance burden? Using new features?