feat: parse string documents to extract the operationName

[tsyirvo]

Following a previous PR from another contributor that allowed getting the OperationName from a GQL operation, I added the possibility to also get it when the document is a string.

Currently, operationName could only be extracted from "regular" queries/mutations, and it wouldn't work for operations passed as strings.

In our current project, all our queries and mutations are auto-generated, and they all are strings, hence the operationName was never resolved and passed.

I just used the parser exposed by graphql to get the actual operation from the string, then used the existing logic for getting and setting the operationName if found.

[tsyirvo]

Since print from graphql/language/printer was already used, I thought there wouldn't be much change by adding the parse method from graphql/language/parser.

The package seems to be already used for other things than static typing now, or am I mistaking?

[jasonkuhrt]

@tsyirvo oh interesting 20f18d3 ... Ok.

Then disregard my comment. I'd rather roll forward on this than back. We can change our policy with regard to the graphql dep. It is not crazy anyways that it would be required as a peer dep or used internally. But will need some thinking perhaps to find the optimal way forward (rather than this current accident).

Meanwhile we can move forward with this.

[jasonkuhrt]

@tsyirvo please add tests and if you can adjust the docs that would be great.

[tsyirvo]

Thank you for your feedback.

I updated the PR, let me know if I need to do something else.

[jasonkuhrt]

LGTM