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
Is your feature request related to a problem? Please describe.
We're trying to replace an older custom graphql gateway, however there are a few scalars that are not prefixed.
When I looked into the details, it seems that there are custom protected scalars causing this: https://github.com/Urigo/graphql-scalars
This is all fine and dandy, but it will cause an issue with the client since we're effectively breaking the schema by replacing the scalars.
We could ignore this type and rename this to create a new endpoint and ask the other teams to use that endpoint, but this would be very dirty.
Describe the solution you'd like
I'd like to opt-in to renaming protected scalars
Describe alternatives you've considered
Cloning an endpoint and their types while migrating.
Breaking the schema for every upstream schema we use, causing issues in production.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We're trying to replace an older custom graphql gateway, however there are a few scalars that are not prefixed.
When I looked into the details, it seems that there are custom protected scalars causing this: https://github.com/Urigo/graphql-scalars
This is all fine and dandy, but it will cause an issue with the client since we're effectively breaking the schema by replacing the scalars.
We could ignore this type and rename this to create a new endpoint and ask the other teams to use that endpoint, but this would be very dirty.
Describe the solution you'd like
I'd like to opt-in to renaming protected scalars
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: