You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure to fork this template and run yarn generate in the terminal.
Please make sure Mesh package versions under package.json matches yours.
2. A failing test has been provided
3. A local solution has been provided
4. A pull request is pending review
Describe the bug
tried adding an additionalResolvers to my schema in my .meshrc.yaml file which has in the requiredSelectionSet one argument which is an integer, but it gets converted to a string.
To Reproduce
Steps to reproduce the behavior:
something like that, integerId is on the database an integer, but when I execute a query in graphql, I get an error that I supplied a string:
Issue workflow progress
Progress of the issue based on the Contributor Workflow
Describe the bug
tried adding an
additionalResolvers
to my schema in my.meshrc.yaml
file which has in therequiredSelectionSet
one argument which is an integer, but it gets converted to a string.To Reproduce
Steps to reproduce the behavior:
something like that, integerId is on the database an integer, but when I execute a query in graphql, I get an error that I supplied a string:
Probably it is due to the string interpolation.
Expected behavior
GraphLQ needs to coerce that value
Environment:
@graphql-mesh/...
:Additional context
The text was updated successfully, but these errors were encountered: