Not reexport types under new name for service functions

[Kavorka79]

Hi,

We are migrating from openapi-typescript-codegen . I have found it hard to use because of the renaming or remapping of types. e.g.
export type GetApiTrackCollectionsPlaylistsByPlaylistIdResponse = PlaylistResponse;

Used by service function

export const getApiTrackCollectionsPlaylistsByPlaylistId = (
    options: Options<GetApiTrackCollectionsPlaylistsByPlaylistIdData>
) => {
    return (options?.client ?? client).get<
        GetApiTrackCollectionsPlaylistsByPlaylistIdResponse,
        GetApiTrackCollectionsPlaylistsByPlaylistIdError
    >({
        ...options,
        url: '/api/track_collections/playlists/{playlistId}',
    });
}; 

I think this takes you away from the domain types and forces you to learn all the types by the service function name. I would much rather receive the PlaylistResponse in the code rather than GetApiTrackCollectionsPlaylistsByPlaylistIdResponse since that is somewhat confusing.

Same for query options that before were in the format.

export const getApiTrackCollectionsPlaylistsByPlaylistId = (
    playlistId: string
) => {

but now are remapped to:

export type GetApiTrackCollectionsPlaylistsByPlaylistIdData = {
    path: {
        playlistId: string;
    };
}; 

It not relevant to know if some thing is passed as a path or query in the domain code using the service function I think. Sure you could use the same name for a path and query parameter but that I think would be on the api builder. Could be solved by adding a prefix if so.

[mrlubos]

I might consider adding this feature as an option. Or did you change your mind about it since? @Kavorka79