-
Notifications
You must be signed in to change notification settings - Fork 132
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
Default GraphQL arguments are not passed into setupFunctions #49
Comments
NeoPhi
added a commit
that referenced
this issue
Mar 11, 2017
NeoPhi
added a commit
that referenced
this issue
Mar 11, 2017
@Urigo Not sure how you feel about pulling in a function that isn't exported by default but handles all of the internals of arguments. |
Urigo
added a commit
that referenced
this issue
Mar 17, 2017
add support for defaultValue to address #49
released as 0.3.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
Versions used
Setup
When defining setup functions like this :
I might be wrong here, since I'm not really familiar with
graphql-subscriptions
but I assumeargs
represents the graphql arguments passed into the subscription query.Considering this query :
args
will be properly set to the expected value :However, when default arguments are defined in the schema like this :
args
will not be set to{ feed: 10 }
as one would expect.Actual outcome
args
is set toExpected outcome
args
set toFailing test
I forked and created a failing test case demonstrating the issue. See here : kouak@820101a
Let me know if you want me to submit a PR with this failing test case.
The text was updated successfully, but these errors were encountered: