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

Custom scalars don't seem to work for schema delegation/remote schemas #525

Closed
schickling opened this issue Dec 6, 2017 · 2 comments
Closed

Comments

@schickling
Copy link
Contributor

Proxying fields with custom scalar values (like DateTime) doesn't seem to work right now using remote schemas/schema delegation.

Here is an example using the GraphQL binding for Github: https://graphqlbin.com/rozCD
Code: https://github.com/graphcool/github-graphql-binding

image

Observation:

Currently the application schema re-exposes the createdAt field using the "original" DateTime! type which leads to the error above. However, when using String! as the field type for createdAt it doesn't throw an error.

  # doesn't work
  createdAt: DateTime!
  # works
  createdAt: String!
@stubailo
Copy link
Contributor

stubailo commented Dec 6, 2017

I think this is a duplicate of #501, thanks for reporting!

@stubailo stubailo closed this as completed Dec 6, 2017
@stubailo stubailo reopened this Dec 6, 2017
@freiksenet
Copy link
Contributor

This looks like an issue with graphql-import. I can use custom scalars fine by using Github.schema directly.

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

3 participants