generated from pascalmartineau/wp-skeleton
refactor: use onServerResponse for auth instead of server api
This commit is contained in:
@@ -17583,12 +17583,6 @@ type RootMutation {
|
||||
input: UpdateUserInput!
|
||||
): UpdateUserPayload
|
||||
|
||||
"""The userSwitchBack mutation"""
|
||||
userSwitchBack(
|
||||
"""Input for the userSwitchBack mutation"""
|
||||
input: UserSwitchBackInput!
|
||||
): UserSwitchBackPayload
|
||||
|
||||
"""The userSwitchTo mutation"""
|
||||
userSwitchTo(
|
||||
"""Input for the userSwitchTo mutation"""
|
||||
@@ -24953,25 +24947,6 @@ enum UserRoleEnum {
|
||||
TRANSLATOR
|
||||
}
|
||||
|
||||
"""Input for the userSwitchBack mutation."""
|
||||
input UserSwitchBackInput {
|
||||
"""
|
||||
This is an ID that can be passed to a mutation by the client to track the progress of mutations and catch possible duplicate mutation submissions.
|
||||
"""
|
||||
clientMutationId: String
|
||||
}
|
||||
|
||||
"""The payload for the userSwitchBack mutation."""
|
||||
type UserSwitchBackPayload {
|
||||
"""
|
||||
If a 'clientMutationId' input is provided to the mutation, it will be returned as output on the mutation. This ID can be used by the client to track the progress of mutations and catch possible duplicate mutation submissions.
|
||||
"""
|
||||
clientMutationId: String
|
||||
|
||||
"""Whether switching back was successful"""
|
||||
success: Boolean
|
||||
}
|
||||
|
||||
"""Input for the userSwitchTo mutation."""
|
||||
input UserSwitchToInput {
|
||||
"""
|
||||
|
||||
Reference in New Issue
Block a user