You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So there is documentation on how to customize queries to provide extra related fields; I was wondering, could you provide documentation on how one can get around customizing builds arguments for mutations on the data provider level?
Just to give more context, we're working on a many-to-many relationship table which doesn't have one (id) primary column; rather, it has a set of columns columnA and columnB which act as the composite key. What I'd like to achieve, is to override the mutation query at the data provider level to then set my own custom arguments as well as augment this on the query document sent out. Is this something possible?
The text was updated successfully, but these errors were encountered:
So there is documentation on how to customize queries to provide extra related fields; I was wondering, could you provide documentation on how one can get around customizing builds arguments for mutations on the data provider level?
Just to give more context, we're working on a many-to-many relationship table which doesn't have one (id) primary column; rather, it has a set of columns columnA and columnB which act as the composite key. What I'd like to achieve, is to override the mutation query at the data provider level to then set my own custom arguments as well as augment this on the query document sent out. Is this something possible?
The text was updated successfully, but these errors were encountered: