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

API 1.0 - Service Request/Response naming #1139

Closed
Tracked by #1131
BrynCooke opened this issue May 24, 2022 · 1 comment
Closed
Tracked by #1131

API 1.0 - Service Request/Response naming #1139

BrynCooke opened this issue May 24, 2022 · 1 comment
Assignees

Comments

@BrynCooke
Copy link
Contributor

BrynCooke commented May 24, 2022

Currently we have:

  • Router - RouterRequest, RouterResponse
  • QueryPlanning - QueryPlannerRequest, QueryPlannerResponse
  • Execution - ExecutionRequest, ExecutionResponse
  • Subgraph - SubgraphRequest, SubgraphResponse

Relates to #1138

In particular QueryPlanner request/response don't match the service name.

@garypen
Copy link
Contributor

garypen commented Jun 9, 2022

Merged into #1138.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants