App uses deprecated API mutations #418

New Issue

Closed

opened 2024-01-10 14:36:26 +02:00 by inex · 0 comments

inex commented

2024-01-10 14:36:26 +02:00

Owner

Expected Behavior

There is a new structure of mutations on the API side: they are grouped just like queries. For example, mutation to move a service should look like this:

mutation MoveService($input: MoveServiceInput!) {
  services {
    moveService(input: $input) {
      ...basicMutationReturnFields
      job {
        ...basicApiJobsFields
      }
    }
  }
}

Actual Behavior

App uses old, flat structure of mutations, for example:

mutation MoveService($input: MoveServiceInput!) {
  moveService(input: $input) {
    ...basicMutationReturnFields
    job {
      ...basicApiJobsFields
    }
  }
}

Steps to Reproduce

Won't cause issues right now due to backwards compatibility.

Context and notes

You may use API docs to view new structure and which mutations are deprecated, for example at https://api.lamia.beauty/graphql

Relevant log output

No response

App Version

0.9.1

Server API Version

2.4.3

Operating System

Android

### Expected Behavior There is a new structure of mutations on the API side: they are grouped just like queries. For example, mutation to move a service should look like this: ```json mutation MoveService($input: MoveServiceInput!) { services { moveService(input: $input) { ...basicMutationReturnFields job { ...basicApiJobsFields } } } } ``` ### Actual Behavior App uses old, flat structure of mutations, for example: ```json mutation MoveService($input: MoveServiceInput!) { moveService(input: $input) { ...basicMutationReturnFields job { ...basicApiJobsFields } } } ``` ### Steps to Reproduce Won't cause issues right now due to backwards compatibility. ### Context and notes You may use API docs to view new structure and which mutations are deprecated, for example at https://api.lamia.beauty/graphql ### Relevant log output _No response_ ### App Version 0.9.1 ### Server API Version 2.4.3 ### Operating System Android