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

Arguments converted to string on additionalResolvers with requiredSelectionSet #4328

Open
4 tasks
gilgardosh opened this issue Aug 18, 2022 · 0 comments
Open
4 tasks

Comments

@gilgardosh
Copy link
Collaborator

Issue workflow progress

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 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:

additionalTypeDefs: |
extend type ExtendType {
value: OtherType!
}
additionalResolvers:
- targetTypeName: ExtendType
targetFieldName: value
sourceName: Server1
sourceTypeName: Query
sourceFieldName: getOtherType
requiredSelectionSet: |
{
integerId
}
sourceArgs:
integerId: {root.integerId}

Probably it is due to the string interpolation.

Expected behavior

GraphLQ needs to coerce that value

Environment:

  • OS:
  • @graphql-mesh/...:
  • NodeJS:

Additional context

@theguild-bot theguild-bot mentioned this issue Aug 21, 2022
@theguild-bot theguild-bot mentioned this issue Sep 28, 2023
This was referenced Apr 30, 2024
This was referenced May 7, 2024
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

No branches or pull requests

1 participant