-
Notifications
You must be signed in to change notification settings - Fork 12
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
COMDOX-828 Services Schema #73
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @jhadobe! 🥇 I made some suggestions based on what I saw in Kevin's migration PR (#71).
@keharper, it might be a good idea to hold off on merging #71 if this PR basically fast tracks our ambitions to eliminate the manually maintained API reference for services. Or perhaps you and Jared should combine efforts if you think the autogenerated content needs to be supplemented with manually written .md. What do you think?
I've noticed that there are some missing descriptions in some of the queries and types. It also looks like there are more types than what we currently have in production, but I'm not sure. It makes me wonder if there are some elements of the schema that should remain private.
Co-authored-by: Jeff Matthews <[email protected]>
Co-authored-by: Jeff Matthews <[email protected]>
This PR demonstrates the possibility of having a separately generated GraphQL schema for services.
It includes:
Staging: https://developer-stage.adobe.com/commerce/services/graphql/reference/
Sanity check, I see the following queries:
These queries match the following services: