api post calls getting typed as void

[gavinthomas-valtech]

Wondering why my api post requests are typed as <void>

What would be in the yaml file that would define this?

how do i get the api team to adjust the yaml file so they are typed?

all get requests are fine

return apiClient<void>({
    url: `/blah/
      method: 'post',
    ...
    ```
    
    
    

[gavinthomas-valtech]

I guess in this case because there is no 201 response specified it's creating when in fact i want it to use the values passed in

[gavinthomas-valtech]

Still can't work this out. The swagger/openapi doc has a schema for a 400

but this is always getting typed as <void>

eg

xport const updateAnonymousElectorApplicationPhotoStatus = (
  Id: string,
  applicationId: string,
  photoId: string,
  updateApplicationPhotoStatusBody: UpdateApplicationPhotoStatusBody
) => {
  return apiClient<void>({
    url: `/${photoId}`,
    method: 'post',
    headers: { 'Content-Type': 'application/json' },
    data: updateApplicationPhotoStatusBody,
  });
};

[gavinthomas-valtech]

You could probably accomplish that using a mutator. I gonna try to do an example for you today

amazing! thanks. Have had great feedback in the team using this client. Looking to do a demo to others in the agency (global agency)

[anymaniax]

I just checked and currently, orval doesn't provide the error type to the mutator could be an improvement to be added to be able to do that. But if you are using something like react-query. It should work properly with the error type too.

[gavinthomas-valtech]

Yes using react query but not as a setting in orval. Creating custom hooks that consume axios functions with a custom mutator. Mainly so we can keep adding to.

This was the post that put me onto this library https://profy.dev/article/react-openapi-typescript

[gavinthomas-valtech]

@anymaniax how did you get on with custom mutator client? Really interested to see this and how it will help

[ellemedit]

this doesn't help generate types for 400 status code responses.