Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support multiple contract-types (Provider Driven Contracts) #32

Open
mefellows opened this issue Feb 2, 2021 · 0 comments
Open

Support multiple contract-types (Provider Driven Contracts) #32

mefellows opened this issue Feb 2, 2021 · 0 comments
Labels
feature request New feature or request feedback-wanted Customer feedback is requested to help validate and refine the feature
Projects
Pactflow Roadmap

Comments

@mefellows
Copy link
Contributor

mefellows commented Feb 2, 2021 •
edited

Following from #4 we will expand the support of contract types that will to others such as:

  • XML/SOAP
  • AsyncAPI
  • Protobufs
  • Avro
  • GraphQL
  • JSON Schema

(List is indicative only at this stage).

This would require an approach for a consumer to publish a non-Pact based contract for verification.

Consideration to support an external plugin approach (likely via an API integration) for cross-contract verification will be included.
@mefellows mefellows added feature request New feature or request feedback-wanted Customer feedback is requested to help validate and refine the feature labels Feb 2, 2021
@mefellows mefellows added this to Planned (1-3 months) in Pactflow Roadmap Feb 2, 2021
@mefellows mefellows moved this from Planned (1-3 months) to Analysis (3-6 months) in Pactflow Roadmap Feb 2, 2021
@mefellows mefellows mentioned this issue Nov 23, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request New feature or request feedback-wanted Customer feedback is requested to help validate and refine the feature
Projects
Pactflow Roadmap
Analysis (3-6 months) / Q2 2024
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mefellows