#603 Support alternative contract types in /contracts/publish endpoint Issue created by mefellows The

contracts[].specification

property in the publish contracts endpoint currently only supports

pact

. In order to support an ecosystem of other contract testing tools - such as case - we should allow other contract types to be submitted. I'm not quite sure of the plans for this field and the validation requirements for it, so I can't comment just now if we should allow a user-defined value, a predefined list or just "other". Given it's a relatively minor change to add new contract types, adding support for the immediate use case of

case

might be a reasonable starting point to avoid relaxing any constraints. P.S. We should create a different GitHub issue template for features :) pact-foundation/pact_broker