pull down to refresh

0 sats \ 11 replies \ @ek 2 Jul freebie \ parent \ on: Why don't stackers donate to rewards anymore? meta
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 🤔
write
preview
110 sats \ 10 replies \ @WeAreAllSatoshi 2 Jul
Yea, here is my code in question. I suspect the mutation is invalid and therefore rejected by the API layer.
reply
0 sats \ 9 replies \ @ek 2 Jul freebie
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.