You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I have a service that is expecting a content-type: application/x-www-form-urlencoded. I am able to write consumer tests to generate the pact file appropriately but whilst running the verifier on the provider side I am getting not supported errors. Is there going to be support enabled for alternative content-types if not is there an alternative approach to run this on the provider side (without using pactman possibly)?
The text was updated successfully, but these errors were encountered:
Currently I have a service that is expecting a content-type: application/x-www-form-urlencoded. I am able to write consumer tests to generate the pact file appropriately but whilst running the verifier on the provider side I am getting not supported errors. Is there going to be support enabled for alternative content-types if not is there an alternative approach to run this on the provider side (without using pactman possibly)?
The text was updated successfully, but these errors were encountered: