Pact V1 does not require pact-ffi, but we are seeing excessive warning in Logs

[amysahli]

We are continuing to use v1 pacts and are not using pact-ffi (intentionally). Its optional for v1, but we are stil seeing excessive logs "Please ensure that the 'pact-ffi' gem is included in your Gemfile for pact/v2 support". As we are trying to cut down logging costs, does it maybe makes sense to not raise this error (or just not log the warning) for v1 clients?

[YOU54F]

Hey,

yeah that is fine, it would be this line here

pact-ruby/lib/pact.rb

Line 11 in 5563e56

warn "Warning: Could not load 'pact/v2': #{e.message} \nPlease ensure that the 'pact-ffi' gem is included in your Gemfile for pact/v2 support."

feel free to propose a pr to remove

Is there any reticence to move to the new pact-ffi based functionality or is this just to avoid upsetting existing tests, and just reducing logging friction.

Would love to hear any feedback, positive or otherwise about the v2 experience.

[YOU54F]

just curious, would you want to potentially avoid the loading block for pact/v2 altogether?

We could use an environment variable to gate the pact/v2 functionality, which is opt-in