Generated mutations by @kubb/swagger-tanstack-query don't add types by to variables about kubb HOT 5 CLOSED

@stijnvanhulle thanks this fix help me a lot but I still have struggle when performing the type checking in TypeScript because TVariables is always of type void even when it receives parameters.

I checked generated function for usePostAPIv!Accountants() and i realized that the type definition is not being passed to TVariables.

i can keep fixing this manually but obviously when execute again kubb --config ./kubb.config.ts my changes are going to be deleted or unsynced

"post": { "tags": [ "Accountants" ], "requestBody": { "content": { "application/json-patch+json; x-api-version=1.0": { "schema": { "$ref": "#/components/schemas/AddAccountant" } }, "application/json; x-api-version=1.0": { "schema": { "$ref": "#/components/schemas/AddAccountant" } }, "text/json; x-api-version=1.0": { "schema": { "$ref": "#/components/schemas/AddAccountant" } }, "application/*+json; x-api-version=1.0": { "schema": { "$ref": "#/components/schemas/AddAccountant" } } } }, "responses": { "200": { "description": "Success", "content": { "text/plain; x-api-version=1.0": { "schema": { "$ref": "#/components/schemas/StringApiResponse" } }, "application/json; x-api-version=1.0": { "schema": { "$ref": "#/components/schemas/StringApiResponse" } }, "text/json; x-api-version=1.0": { "schema": { "$ref": "#/components/schemas/StringApiResponse" } } } } }

from kubb.

@Jesus-Hernandez23 Can you add the function for usePostAPIv!Accountants(). Need to see which types are getting used there causing the void.

from kubb.

@Jesus-Hernandez23 Can you add the function for usePostAPIv!Accountants(). Need to see which types are getting used there causing the void.

sure this is generated code:

import { useMutation, UseMutationOptions } from '@tanstack/react-query';
import client from '@kubb/swagger-client/client';
import type { PostApiV1AccountantsMutationResponse } from '.\\..\\models\\PostApiV1Accountants';

/**
 * @link /api/v1/Accountants
 */
export function usePostApiV1Accountants<TData = PostApiV1AccountantsMutationResponse, TError = unknown>(options?: {
  mutation?: UseMutationOptions<TData, TError>;
}) {
  const { mutation: mutationOptions } = options ?? {};

  return useMutation<TData, TError>({
    mutationFn: () => {
      return client<TData, TError>({
        method: 'post',
        url: `/api/v1/Accountants`,
      });
    },
    ...mutationOptions,
  });
}

from kubb.

@Jesus-Hernandez23 This Seems to be an issue related to the paths that are getting generated. Node.js always uses / but for some reason we have a bug that makes use of the platform and converts / to \ for Windows.

See '.\\..\\models\\PostApiV1Accountants';

Will be fixed with chore/e2eWindows( and also added a Github actions for Windows to be 100% sure.

from kubb.

Aha found the issue, we had hardcoded to always use application/json as requestBodyType but here you are using application/json; x-api-version=1.0 which was not getting found by our generator.

I will open a PR so it's not hardcoded anymore :)

from kubb.