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.

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

GraphQL #53

Open
mefellows opened this issue Nov 23, 2021 · 3 comments
Open

GraphQL #53

mefellows opened this issue Nov 23, 2021 · 3 comments

Comments

@mefellows
Copy link
Contributor

Bi-directional support for GraphQL

@QuitHub
Copy link

QuitHub commented May 16, 2024

@mefellows @YOU54F Hi folks, we are very keen for this feature. I can see it hasn't moved in the roadmap for a year and a half but would be a massive feature for us! An update would be greatly appreciated!

@mefellows
Copy link
Contributor Author

Hi @QuitHub, this feature has yet to be prioritised at this moment. Our customers are advised to use regular Pact/CDC testing for GraphQL in the meantime.

We would absolutely appreciate input (problem statements, ideas or otherwise) here as that will help us with prioritisation and design.

@YOU54F
Copy link
Member

YOU54F commented Jun 26, 2024

For inspiration, please consider https://github.com/pactflow/swagger-mock-validator

this is the basis for our oas comparison, which checks a pact file is a valid subset of the OAS.

anyone is free to consider the development of such a tool, but currently the team are working on other items and this hasn't made it onto the roadmap.

The pact plugin framework would be a better place, with the generation of a dedicated graphql plugin

pact-foundation/roadmap#94

@mefellows mefellows moved this to Themes / Exploring (>12 months) in Pactflow Roadmap Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Themes / Exploring (>12 months)
Development

No branches or pull requests

3 participants