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.

Sign up for GitHub

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

Jump to bottom

Schema Awareness #437

Closed
Tracked by #76
, #596 ,  #597 ,  #598 ,  #601
...
dotansimha opened this issue Feb 12, 2024 · 0 comments · Fixed by #444
Closed
Tracked by #76
, #596 ,  #597 ,  #598 ,  #601
...

Schema Awareness #437

dotansimha opened this issue Feb 12, 2024 · 0 comments · Fixed by #444
Labels
feature A new feature

Comments

@dotansimha
Copy link
Member

dotansimha commented Feb 12, 2024 •
edited

At the moment, Conductor does not know about the upstream schema it's going to execute (the exception is the Federation handler that requires a Supergraph SDL to operate).

By adding support for loading (and reloading) the upstream SDL (in graphql source), we can enrich the execution and take control over validation of the incoming GraphQL operations (#6), and also implement other things like schema filters (#436).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature A new feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: schema awareness (+fixed root logger) the-guild-org/conductor
1 participant
@dotansimha