Steve Taylor

Hi I am having this same issue - seems to be the same as issue #310 These did exist prior to 6.5.0 but were stripped out in https://github.com/braintree/braintree_php/commit/e35c2a2d74a10e9cec5932506486e4b8bccfa4ba

I just came along to second this issue - it seems really strange that they were stripped out? We use phpstan for static analysis, and without these property annotations, all...

We were getting this on v18.18.0 and have rolled back to v18.17.1 for now ``` #26 6.723 SyntaxError: Unexpected token in JSON at position 56 #26 6.723 at JSON.parse ()...

Thank you @tienvx for all your hard work. When we initially adopted Pact a year ago we used the Ruby standalone provider, before moving to the Rust standalone in march....

I ended up moving to the rust standalone provider verifier, it has all of these features implemented already as well as the v3 and v4 pact specifications https://docs.pact.io/implementation_guides/rust/pact_verifier_cli Given its...

Hi, I am very keen to get this working, and will pick up where @hhhonzik left off if needed, looks like the pull requests were fairly far along?

I have added the remaining generators and some tests to the pact-ruby project https://github.com/pact-foundation/pact-ruby/pull/273

It requires https://github.com/pact-foundation/pact-support/pull/97 in order to pass the tests I have been using this as part of my own build of pact-provider-verifier successfully for the last month I would welcome...

If we could please get https://github.com/pact-foundation/pact-support/pull/97 (which is only minor) merged over in that project, then this pull request should start passing tests here🤞

Thank you! I've updated the pact.gemspec to use the new pact-support version