Support client language in verification results

[mefellows]

When the verification results are sent to the broker, the implementation values are hard coded to the Pact-Rust and the version of the crate:

"verifiedBy": { "implementation": "Pact-Rust", "version": "1.0.4" },

It would be ideal for the client language (JS, Go etc.) to be represented in here somewhere, so that we can display them in the Pact Broker interface, help when debugging etc.

Perhaps we need a way to represent both the wrapper language and the core?

[github-actions]

👋 Hi! The 'smartbear-supported' label has just been added to this issue, which will create an internal tracking ticket in PactFlow's Jira (PACT-1240). We will use this to prioritise and assign a team member to this task. All activity will be public on this ticket. For now, sit tight and we'll update this ticket once we have more information on the next steps.

See our documentation for more information.

[mefellows]

It looks like there was some activity on this request, but it's not clear how client languages should pass in their details.

I believe the client language for the verifier is passed in to pactffi_verifier_new_for_application which accepts a name and version. How does the consumer side get passed in?

[rholshausen]

Consumer side? This is for the verification results. It's the provider side.

[mefellows]

Oh yeah. I can read ticket headlines :P. I think we can close this.