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
I am building a login mutation (operation) but have multiple backend login providers that will return user data. I'm currently federating these manually in a single defmutation - but different resolvers return different levels of user data - which I map manually into whatever properties I define in ::pco/output - but of course, with resolvers, it would be fine to return as-is and provide resolvers to allow clients to do the login and request whatever they want.
So, my question is: is there a hook that I can use to force a generic request for an operation such as "login" to be satisfied by a specific mutation?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
I am building a login mutation (operation) but have multiple backend login providers that will return user data. I'm currently federating these manually in a single defmutation - but different resolvers return different levels of user data - which I map manually into whatever properties I define in ::pco/output - but of course, with resolvers, it would be fine to return as-is and provide resolvers to allow clients to do the login and request whatever they want.
So, my question is: is there a hook that I can use to force a generic request for an operation such as "login" to be satisfied by a specific mutation?
Beta Was this translation helpful? Give feedback.
All reactions