gateway merged
GraphQL federation gateway
Current state
Languages
- TypeScript: 105,732 bytes
- Shell: 57,080 bytes
- JavaScript: 1,779 bytes
- Dockerfile: 524 bytes
CI
success — CI
Last commit
4cca68f27a9615a33882f85ff3a4517fcc8ab0d8 (2026-08-11T10:08:26+03:00)
Module/package dependency graph (dependency-cruiser, folder-collapsed)
23 node(s), 37 edge(s) — scroll to zoom, drag to pan, click a node for details.
Circular dependencies (madge): 0
Class diagram (UML, via ts-morph)
13 node(s), 0 edge(s) — scroll to zoom, drag to pan, click a node for details.
GraphQL API
CI/CD pipeline (all workflows)
3 node(s), 0 edge(s) — scroll to zoom, drag to pan, click a node for details.
Outgoing relationships
None detected.
Incoming relationships
None detected.
Target state (spec-kit)
specs/001-graphql-gateway/spec.md— Feature Specification: GraphQL Gateway
As a client application, I want to send a single GraphQL request to one gateway endpoint and receive data composed from whichever backend services own it (starting with the auth service), so that I don't need to know or care how the platform's services are split up.
ADR files: 0