Support alternative contract types in /contracts/publish endpoint
mefellows opened this issue · 1 comments
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 :)
👋 Hi! The 'smartbear-supported' label has just been added to this issue, which will create an internal tracking ticket in PactFlow's Jira (PACT-878). We will use this to prioritise and assign a team member to this task. All activity will be public on this ticket. For now, sit tight and we'll update this ticket once we have more information on the next steps.
See our documentation for more information.