Thank you for this proposal. As you can see from the checklist, the idea is that you first create an issue with an API proposal so we can discuss the consequences. But since we know each other let's see if we can take this PR further 🫢

When writing the API proposal, please check whether asserting signature fingerprint only is possible and - maybe - easier to use.

Thank you for this proposal. As you can see from the checklist, the idea is that you first create an issue with an API proposal so we can discuss the consequences. But since we know each other let's see if we can take this PR further 🫢

I know. I had the code already, and I was not sure my self yet which API to propose. That's the reason I already started this PR. But if this a desired extension to the API, and if not, what to add (or to add this at all) definitionally should be discussed too.

It looks promising, but let's discuss the API in a GH issue first.
The issue template contains questions that help ensuring we're on the same line and reach the better design.

That people already started commenting on the implementation before the shape was agreed upon proves the need to keep these thing separate.

@dennisdoomen :Note that locally my build fails, as it claims that C#11 features are not available, and all warnings are handled as errors. Can someone enlighten me on why that could happen?

Do you have the .NET 7 SDK installed? Our global.json file should specify the minimum required version.

Do you have the .NET 7 SDK installed? Our global.json file should specify the minimum required version.

Yes I have. Both for my company and multiple open source projects I work on require that. As mentioned, also the thing that (and that only happens for this solution) all warnings are handled as errors is strange.

Yes I have. Both for my company and multiple open source projects I work on require that. As mentioned, also the thing that (and that only happens for this solution) all warnings are handled as errors is strange.

I recommend joining our Slack to have a more efficient discussion. You can use this invite.

Pull Request Test Coverage Report for Build 5705024583

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 29 of 29 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.006%) to 97.217%

Totals
Change from base Build 5672891851:	-0.006%
Covered Lines:	12890
Relevant Lines:	13132

💛 - Coveralls