Matt Fellows
Matt Fellows
I think one way to fix it with backwards compatibility, would be to lookup both the description (first) and fallback to the state names if no handler is found that...
I think this might be related to https://github.com/pact-foundation/pact-reference/issues/387
Are you getting the same error or a different one? If the certificate is valid, it shouldn't be erroring obviously. Can you share the certificate here for review?
Feels like it's in here somewhere: https://github.com/pact-foundation/pact-reference/blob/master/rust/pact_matching/src/lib.rs#L1629-L1661 It uses `is_equivalent_to` which has the following definition: ``` /// Equals, ignoring attributes if not present on self pub fn is_equivalent_to(&self, other: &ContentType)...
This RFC is now a year old. Given there are no objections, I think it's time we merge this!
Thanks Tim!
I've also tagged several other maintainers for their visibility.
> I think your explanation above is a good one, like this process covers the common elements of the ecosystem (such as the Spec and FFI) and not the language-specific...
I actually wasn't aware of that feature - definitely happy for a PR, thank you.
Very picky, but could you please reword your commit message as per : https://github.com/pact-foundation/pact-go/blob/master/CONTRIBUTING.md#commit-messages I'd suggest ``` docs: update typo in install instructions ``` The reason is commit messages are...