Question about the format of callback's 'input' argument about operation-hooks HOT 3 CLOSED

The data from the first code block is generated by the lookahead system/etc. It can change in patch versions and is heavily influenced by user input in the query itself. You are not expected to deal with anything that contains an @ symbol; these implementation details are internal.

This question is not one you should be asking; could you share what you're trying to achieve so that I can perhaps guide you down a better path?

from operation-hooks.

Thanks @benjie
I'm working on a micro-payment system for graphql queries. I'm using the after hook to request a payment from the client based on the size of the response payload. The request is throttled until payment is received. I have all the logic working well except:

• I need to be able to generate a hash of the payload that the client can later match against the payments they made (an alternative solution might be attaching the hash of the input to the payload)
• I also need the payload to be in its final form when pricing the data to enable the client to later verify that they were charged the right amount

Would really appreciate your advice on how I can accomplish this.

from operation-hooks.

As discussed in chat, this needs to be done outside of GraphQL after GraphQL has resolved. One option is to use a server plugin for this, it should work for queries and mutations but we don’t have hooks for post-processing subscription bodies currently.

from operation-hooks.