Handle JSON null operationName properly
klarstrup opened this issue · comments
Currently it casts it to a "null" string and then complains when it finds no operation by that name in the query:
Expected behavior would be to assume an unnamed operation.
Looking at this, the error is somewhere in our (internal) HTTP handler. I've pushed a fix there and if the error persists, we'd have to fix it in that repository as well. Sorry for the bug.