This repository has been archived by the owner on Apr 15, 2020. It is now read-only.
forked from ardatan/graphql-tools
-
Notifications
You must be signed in to change notification settings - Fork 5
After transform custom scalars are broken #9
Comments
This may be working as intended, transformSchema actually wraps the original schema and delegates to it, so we have to serialize with original schema and then parse with new. in general, shouldn't the serialize and parse functions reverse each other? |
I think this is working as designed: consider changing code as below to gain visibility:
|
yaacovCR
added a commit
that referenced
this issue
Sep 22, 2019
yaacovCR
added a commit
that referenced
this issue
Sep 22, 2019
yaacovCR
added a commit
that referenced
this issue
Sep 22, 2019
yaacovCR
added a commit
that referenced
this issue
Sep 22, 2019
yaacovCR
added a commit
that referenced
this issue
Sep 22, 2019
yaacovCR
added a commit
that referenced
this issue
Sep 22, 2019
yaacovCR
added a commit
that referenced
this issue
Oct 3, 2019
yaacovCR
added a commit
that referenced
this issue
Oct 25, 2019
yaacovCR
added a commit
that referenced
this issue
Oct 25, 2019
yaacovCR
added a commit
that referenced
this issue
Nov 4, 2019
yaacovCR
added a commit
that referenced
this issue
Dec 31, 2019
yaacovCR
added a commit
that referenced
this issue
Dec 31, 2019
yaacovCR
added a commit
that referenced
this issue
Jan 8, 2020
yaacovCR
added a commit
that referenced
this issue
Jan 21, 2020
yaacovCR
added a commit
that referenced
this issue
Feb 27, 2020
yaacovCR
added a commit
that referenced
this issue
Mar 26, 2020
yaacovCR
added a commit
that referenced
this issue
Mar 26, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After running this the output is:
so the value passed to
serialize
is different than before schema was transformed.The text was updated successfully, but these errors were encountered: