According to https://spec.graphql.org/June2018/#sec-String-Value
A multiline like

"Lore ipsum
One
Two"

is not allowed, for multiline strings, block strings (with triple quotes) are required.

Does this still fail for proper block strings?

According to https://spec.graphql.org/June2018/#sec-String-Value A multiline like

"Lore ipsum
One
Two"

is not allowed, for multiline strings, block strings (with triple quotes) are required.

Does this still fail for proper block strings?

About the documentation thx a lot, now are integrated all the escaped characters in ae3d44c #454

I will show you with an example

1. The stringValueNode parameter contains this text: "Lore ipsum\nOne\nTwo";
2. stringValueNode.isBlock will return false since is not """
3. When printNode is called, stringValueNode will be displayed as

"Lore ipsum
One
Two"

causing a problem when encoding the query with the gql_link RequestSerializer

According to https://spec.graphql.org/June2018/#sec-String-Value A multiline like

"Lore ipsum
One
Two"

is not allowed, for multiline strings, block strings (with triple quotes) are required.

Does this still fail for proper block strings?

Is is possible also that the Token is not computing the strings correctly?

Is is possible also that the Token is not computing the strings correctly?

If you point me to any nontrivial piece of code and ask me "is it possible that there is a bug" I'll always say yes ;)

Do you have any specific lead to a potential issue?

According to https://spec.graphql.org/June2018/#sec-String-Value A multiline like

"Lore ipsum
One
Two"

is not allowed, for multiline strings, block strings (with triple quotes) are required.
Does this still fail for proper block strings?

About the documentation thx a lot, now are integrated all the escaped characters in ae3d44c #454

I will show you with an example

1. The stringValueNode parameter contains this text: "Lore ipsum\nOne\nTwo";
2. stringValueNode.isBlock will return false since is not """
3. When printNode is called, stringValueNode will be displayed as

"Lore ipsum
One
Two"

causing a problem when encoding the query with the gql_link RequestSerializer

gql/links/gql_link/lib/src/request_serializer.dart

Line 17 in 2dad214

"query": printNode(request.operation.document),

Yes, that's true; There is an issue.