Poor error messages when generating clients for endpoints with no OperationId

[Numpsy]

Hi, I had a go at using the provider against an OpenApi 3 spec generated from an ASP.Net Core minimal API project which didn't have any names set on the endpoints (which seems to generate a spec with no OperationId) and got some errors like

Note the Operation '' which doesn't tell you which endpoint the error is actually coming from.

This is quite trivial and fixed by adding operation ids to the spec, but was wondering if maybe the error handling code around https://github.com/fsprojects/SwaggerProvider/blob/656ac330f008774529c09b3357a939c985991933/src/SwaggerProvider.DesignTime/v3/OperationCompiler.fs#L123 should use the path or something if there is no OperationId, as it already seems to do elsewhere?

Thanks.