Oh, I think it's broken because GraphQL also validates that the fields you want to resolve actually exist.

So it needs to be `response { id }` in your body instead of `id`.

Same with @hn. 

Yea, [here](https://github.com/SatsAllDay/sn-daily-mining/blob/main/sn.ts#L212) is my code in question. I suspect the mutation is invalid and therefore rejected by the API layer.

WeAreAllSatoshi

Ohh, we did indeed change the response for every mutation. The previous response is now nested inside a `response` property. We did that because a mutation might also return an invoice now next to `response` in `invoice`.

But I think the arguments haven't changed.

Seems like I also need to fix @hn but that would mean something about the arguments did change 🤔

Why don't stackers donate to rewards anymore?

grayruby

Seems like my `upsertComment` mutation is not successful. I am not logging the error response, but my code is failing to parse the response data, looking for `data.upsertComment`. Any new params or signature changes to that mutation? I can look myself too, don't stop anything important 