Remove operation name from the regex and default to query

[jkimbo]

Fixes #1003

[eabruzzese]

@jkimbo this will break if there are multiple operations being sent. For example:

query FirstOperation {
  ...
}

subscription SecondOperation {
  ...
}

When you click the button to execute the operation, it'll have you choose the operationName from the dropdown. If you choose SecondOperation, the regex in this PR will match query, and won't send it over the websocket -- causing the operation to fail.

Let me take a look at that issue.

[jkimbo]

Good point @eabruzzese . Could check if operationName is defined and only use it in the regex if it is? Also I found this in the graphiql examples: https://github.com/graphql/graphiql/blob/main/examples/graphiql-cdn-subscriptions/index.html#L61-L74

But it requires the parse method which I assume comes from graphql. That might be a more robust option though.

[eabruzzese]

@jkimbo yeah, I saw that and tried to incorporate the parser, but couldn't get it working because of the format of the graphql CDN package (it doesn't have a UMD, and it also seemed like overkill for just detecting the operation type).

I like your idea there: if there's no operation name, just don't include it in the regex. The fallback to query is probably a good idea too. That should solve most cases for now. I'll try to incorporate the parser again tonight.

[eabruzzese]

@jkimbo I think you could just change graphQLParams.operationName + to (graphQLParams.operationName || '') + to get it working, yeah?

[eabruzzese]

@jkimbo Just tested with this branch. Works as expected.