I stumbled upon this issue while porting my sourcehut.pl package to use the new library(http/graphql):
As per https://spec.graphql.org/draft/#StringCharacter, GraphQL does not allow for line terminators (\r and/or \n) to occur in regular string literals (they are allowed in block strings, which use """ instead of " as delimiters). This is in contrast to Prolog strings, which do not impose this limitation.
Hence, line terminators that occur in Prolog strings must be escaped This mismatch gave rise to an issue when they are incorporated in GraphQL, e.g. via quasi-quotation.
This PR adds escaping for line terminators in strings written as part of graphql_document_to_{codes,string}/3, and adds a relevant test case.
I stumbled upon this issue while porting my
sourcehut.plpackage to use the newlibrary(http/graphql):As per https://spec.graphql.org/draft/#StringCharacter, GraphQL does not allow for line terminators (
\rand/or\n) to occur in regular string literals (they are allowed in block strings, which use"""instead of"as delimiters). This is in contrast to Prolog strings, which do not impose this limitation. Hence, line terminators that occur in Prolog strings must be escaped This mismatch gave rise to an issue when they are incorporated in GraphQL, e.g. via quasi-quotation.This PR adds escaping for line terminators in strings written as part of
graphql_document_to_{codes,string}/3, and adds a relevant test case.