fix: incorrect import path for runtimeConfigPath in generated client.gen.ts

[Dima-Bulavenko]

What's the problem?

When using runtimeConfigPath with a relative path in a nested output directory, the generated import path is incorrect. The generator doesn't calculate the proper relative path from the generated file to the config file.

Folder Structure

root/opentapi-ts.config.ts

import { defineConfig } from '@hey-api/openapi-ts';

export default defineConfig({
  input: './openapi.json',
  output: './gen',
  plugins: [
    {
      name: '@hey-api/client-axios',
      runtimeConfigPath: './client_config.ts',
    },
  ],
})

root/client_config.ts

import type { CreateClientConfig } from './gen/client.gen';

export const createClientConfig: CreateClientConfig = (config) => ({
  ...config,
  baseURL: 'http://localhost:8000',
});

root/gen/client.get.ts

// This file is auto-generated by @hey-api/openapi-ts

import { type ClientOptions, type Config, createClient, createConfig } from './client';
import { createClientConfig } from './client_config.ts'; // THIS IMPORT IS INCORRECT, IT SHOULD REFERENCE '../client_config.ts'
import type { ClientOptions as ClientOptions2 } from './types.gen';

/**
 * The `createClientConfig()` function will be called on client initialization
 * and the returned object will become the client's initial configuration.
 *
 * You may want to initialize your client this way instead of calling
 * `setConfig()`. This is useful for example if you're using Next.js
 * to ensure your client always has the correct values.
 */
export type CreateClientConfig<T extends ClientOptions = ClientOptions2> = (override?: Config<ClientOptions & T>) => Config<Required<ClientOptions> & T>;

export const client = createClient(createClientConfig(createConfig<ClientOptions2>()));

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0faccd4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@Dima-Bulavenko is attempting to deploy a commit to the Hey API Team on Vercel.

A member of the Team first needs to authorize it.