Pact 2.0 RSpec integration conflicts with pact-support 1.26.1 (latest)

[soulcutter]

Both pact 2.0 and pact-support (latest, 1.21.6) have a pact/rspec defined.

Which one do you get when you require "pact/rspec"? It depends on bundler load path ordering. In most cases it seems to load pact-support's and NOT pact's, and that means that pact's rspec integration is never loaded.

Example irb session:

>> $:.select { _1.include? "pact" }
=> 
["/Users/bradleyschaefer/.local/share/mise/installs/ruby/3.4.9/lib/ruby/gems/3.4.0/gems/pact-support-1.21.6/lib",
 "/Users/bradleyschaefer/.local/share/mise/installs/ruby/3.4.9/lib/ruby/gems/3.4.0/gems/pact-2.0.0/lib",
 "/Users/bradleyschaefer/.local/share/mise/installs/ruby/3.4.9/lib/ruby/gems/3.4.0/gems/pact-ffi-0.4.28.0-arm64-darwin/lib"]

>> require "pact/rspec"
=> true

>> PactConsumerDsl # pact/rspec from pact would have loaded this
/Users/bradleyschaefer/Projects/domain-insight-service/spec/service_providers/pact_helper.rb(irb):3:in '<main>': uninitialized constant PactConsumerDsl (NameError)

The consequence is that you won't get things you need like http_pact_provider in an RSpec.describe tagged with pact: true, pact_entity: :provider

Solution

Unsure.

Is pact-support known/intentionally incompatible with 2.0?
Should pact-support be removed from projects that had been using it?

[YOU54F]

👋🏾

Thanks for raising,

This require for 'pact` shouldn't be there, that is a hangover from the v2 migration

pact-ruby/lib/pact/rspec.rb

Line 4 in 0ca5246

require 'pact'

pact-support isn't required at all for pact-ruby 2.0, but it ideally shouldn't be incompatible, as we use it in two projects which still rely on pact-support

• https://github.com/pact-foundation/pact_broker
• https://github.com/pact-foundation/pact_broker-client

I'll test these out with v2 and check

[soulcutter]

If it helps, I reported this based on a real problem in an application, not a hypothetical issue. I have pinned to 1.x as a result.

[YOU54F]

are you needing to use something in pact-support in your project?

i’ll have a think about the best way forward here. maybe avoiding loading pact-support rspec file if pact-ffi is defined

open to suggestions

[soulcutter]

If you want to be able to load both of them, they should have different paths. I’d suggest pact/rspec and pact/support/rspec

[YOU54F]

I don’t, pact-support is no longer a requirement and ultimately will be archived. I am asking why you are loading both in your project? Is there something you require from pact-support that isn’t available in pact-ruby v2