openapi-fetch Type instantiation is excessively deep and possibly infinite.

[vovsemenv]

I have the code with 2 api calls - one with "openapi-fetch" other with "openapi-react-query"
but only "openapi-react-query" have actual error on paths that didn't exist,
"openapi-fetch"generates the Type instantiation is excessively deep and possibly infinite.

Because of that vscode autocomplete didn't work in case with "openapi-fetch"

import type { paths } from "app/typings/__generated/api";

import createFetchClient from "openapi-fetch";
import createClient from "openapi-react-query";

export const fetchClient = createFetchClient<paths>({});
export const $api = createClient(fetchClient);

fetchClient.GET("/api/d");
// ^ Type instantiation is excessively deep and possibly infinite.
$api.useQuery("get", "/api/sdf");
// ^ Argument of type '"/api/sdf"' is not assignable to parameter of type 'PathsWithMethod<paths, "get">'

fetchClient.GET("/api/accessgroup");
// ^ Existing url works fine
$api.useQuery("get", "/api/accessgroup");
// ^ Existing url works fine

api.d.ts.zip

[drwpow]

As you discerned, this error does appear when there’s an actual error. It’s tough to control the output for what TypeScript shows beyond throwing an error. There are no known instances where this happens for a legitimate path. But agreed the error could be more helpful.

Flagged as an “enhancement” as in “this error message should be improved” although we are limited by what TypeScript allows (since it’s the one that shows that error). PRs are welcome for anyone that can improve this! (And bonus points if it can be tested)

[vovsemenv]

Yes i understand that😅 Just really strange to see that the same thing works in react-query version