Modifying queries/mutations before they are sent to an API

[LaurianeDPWaya]

Hello all,

I am currently trying to integrate the RxDB library that is in the frontend of my application with a REST API, as I am using RxDB with its GraphQL replication tool I needed something to convert my queries and mutations to something a REST API could respond to, that's where GraphQL-Mesh comes in!

The way RxDB works is that it is either pulling or pushing data, pulling corresponds to a GET request and is easy enough to convert through Mesh to return the data I want, but pushing corresponds to everything else that modifies the database.
As such I would need to intercept all mutations sent by my frontend app and would like to add some logic to Mesh so that each "push" is converted to a GraphQL query that exists in my REST API's schema.

I have tried using resolvers to solve this:

transforms:
  - resolversComposition:
      mode: bare
      compositions:
        - resolver: "Query.*"
          composer: ./resolvers/rxdb-pull#rxDBPull
        - resolver: "Mutation.*"
          composer: ./resolvers/rxdb-pull#rxDBPush

I can currently modify what my REST API is sending back to the frontend in my rxDBPull method by modifying the response directly:
const response = next(root, newArgs, context, info);

But I am having a hard time similarly modifying the request, my modifications seem to be affecting the request, but not the response.

//TEST removes field "isChecked" from selection query
let value = info.fieldNodes[0].selectionSet.selections[1];
info.fieldNodes[0].selectionSet.selections.filter(item => item !== value);

Here when I check the value of "info" it has been modified by my intervention, however the response still contains the field "isChecked".

TL;DR
In summary, is there a way for Mesh to affect queries and mutations before they are sent to an API, possibly with a resolver?

Thank you for sharing any insight you might have on this!