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.
graphql-eslint dosn't support AWS supported scalars and return Unknown type error. The main supported AWS scalars for AppSync are :
AWSDate, AWSDateTime, AWSEmail, AWSIPAddress, AWSJSON, AWSPhone, AWSTime, AWSTimestamp, AWSURL
it currently breaking the pipelines with this error:
0:0 error Parsing error: [graphql-eslint] Error while loading schema: Unknown type "AWSJSON".
Describe the solution you'd like
add these types as accepted scalar types:
AWSDate, AWSDateTime, AWSEmail, AWSIPAddress, AWSJSON, AWSPhone, AWSTime, AWSTimestamp, AWSURL
Describe alternatives you've considered
Atleast skip checking these types to stop pipelines from failing
The text was updated successfully, but these errors were encountered:
graphql-eslint dosn't support AWS supported scalars and return Unknown type error.
normal behaviour graphql-eslint takes input schema, and builds it, if some type is missing how he should know it?
Do you have any ideas on how to include them for AWS projects? include by default is not a good idea since the user can have their own scalar AWSEmail, maybe via some option in parserOptions or graphql-config?
Is your feature request related to a problem? Please describe.
graphql-eslint dosn't support AWS supported scalars and return Unknown type error. The main supported AWS scalars for AppSync are :
AWSDate, AWSDateTime, AWSEmail, AWSIPAddress, AWSJSON, AWSPhone, AWSTime, AWSTimestamp, AWSURL
it currently breaking the pipelines with this error:
Describe the solution you'd like
add these types as accepted scalar types:
AWSDate, AWSDateTime, AWSEmail, AWSIPAddress, AWSJSON, AWSPhone, AWSTime, AWSTimestamp, AWSURL
Describe alternatives you've considered
Atleast skip checking these types to stop pipelines from failing
The text was updated successfully, but these errors were encountered: