We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Progress of the issue based on the Contributor Workflow
Make sure to fork this template and run yarn generate in the terminal. Please make sure the GraphQL Tools package versions under package.json matches yours.
Make sure to fork this template and run yarn generate in the terminal.
yarn generate
Please make sure the GraphQL Tools package versions under package.json matches yours.
package.json
Describe the bug
When mocking a nested root query, I can override any simple field, but overriding resolver fields doesn't work.
To Reproduce
Here is a test showing the problem
You can run the test in my fork, or just copy over the test.
Expected behavior
I expect returnStringArgument to have the value Overridden, but I get the default string value Hello World.
returnStringArgument
Overridden
Hello World
Environment:
@graphql-tools/mock
Additional context
I'm trying to fix a problem we are seeing in another tool graphql-fakester
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue workflow progress
Progress of the issue based on the Contributor Workflow
Describe the bug
When mocking a nested root query, I can override any simple field, but overriding resolver fields doesn't work.
To Reproduce
Here is a test showing the problem
You can run the test in my fork, or just copy over the test.
Expected behavior
I expect
returnStringArgument
to have the valueOverridden
, but I get the default string valueHello World
.Environment:
@graphql-tools/mock
:Additional context
I'm trying to fix a problem we are seeing in another tool graphql-fakester
The text was updated successfully, but these errors were encountered: