The problem to work through.
Publishing a GraphQL API involves more than accepting a schema. Its structure needs to be understood, useful documentation needs to be generated, and the publishing lifecycle needs to stay consistent across services.
What I worked on.
- Implemented an end-to-end GraphQL publishing flow across four Java and Python microservices.
- Built a Flask service using graphql-core to parse SDL schemas and generate interactive HTML API documentation.
- Integrated the flow with the gateway publish and unpublish lifecycle.
- Resolved null-pointer and action-routing defects, along with time-of-check/time-of-use and path-validation vulnerabilities.
What the work made possible.
Connected schema processing, documentation generation, and portal publishing in one lifecycle.
Improved the handling of failure paths and addressed security defects in the publishing flow.