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

Introspection queries don't support @oneOf #4077

Open
maciesielka opened this issue May 2, 2024 · 2 comments · May be fixed by #4078
Open

Introspection queries don't support @oneOf #4077

maciesielka opened this issue May 2, 2024 · 2 comments · May be fixed by #4078

Comments

@maciesielka
Copy link

maciesielka commented May 2, 2024

Related to the issue in #3968, it doesn't appear that the introspection query is selecting the isOneOf field from the server, as defined by the RFC.

This has downstream effects like preventing this introspection response from powering codegen that uses that flag to enforce mutual exclusivity amongst the arguments.

I've attempted to add this functionality in #4078

@maciesielka maciesielka changed the title Add @oneOf support to introspection queries Introspection queries don't support @oneOf May 2, 2024
@maciesielka maciesielka linked a pull request May 2, 2024 that will close this issue
@JoeM1990
Copy link

In connection with the problem in #3968, it doesn't seem that the RFC-defined isOneOf field is being selected from the server by the introspection query.

This has side effects, such as stopping codegen that utilizes that flag to impose mutual exclusivity among the arguments from being powered by this introspective answer.

I've tried to incorporate this feature into #4078.

@JoviDeCroock
Copy link

What do you mean precisely @JoeM1990 it is defined here that isOneOf is a valid field on an input-object

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

Successfully merging a pull request may close this issue.

3 participants