@ardeois to begin with, thanks for all the work being put in this plugin.
In our app we use AWS Appsync Scalars, which add specific GraphQL types for dates. Unfortunately, one of them is AWSTimeStamp which maps to a timestamp (number).
Currently, as it stands, this plugin translates all the custom scalars into strings which breaks our TS validation, since we expected a number.
Given the fact that you said that custom scalars need to accept custom definitions, my question would be whether you have immediate plans to support it and/or whether you would be open to accepting PRs to add this functionality.
@ardeois to begin with, thanks for all the work being put in this plugin.
In our app we use AWS Appsync Scalars, which add specific GraphQL types for dates. Unfortunately, one of them is
AWSTimeStampwhich maps to a timestamp (number).Currently, as it stands, this plugin translates all the custom scalars into strings which breaks our TS validation, since we expected a
number.Given the fact that you said that custom scalars need to accept custom definitions, my question would be whether you have immediate plans to support it and/or whether you would be open to accepting PRs to add this functionality.
Thanks in advance