veza/apps/web/src/services/generated/logging/logging.ts
senke 34a0547f78 chore(web): drop orval multi-status response wrapper from generated types
orval v8 emits a `{data, status, headers}` discriminated union per
response code by default (e.g. `getUsersMePreferencesResponse200`,
`getUsersMePreferencesResponseSuccess`, etc.). That wrapper layer was
purely synthetic — vezaMutator returns `r.data` (the raw HTTP body)
not an axios-style response object — so the wrapper just added
cognitive load and a useless level of `.data` ladder for consumers.

Set `output.override.fetch.includeHttpResponseReturnType: false` and
regenerated. Generated functions now declare e.g.
`Promise<GetUsersMePreferences200>` directly; consumers see the
backend envelope `{success, data, error}` shape (which is what the
backend actually returns and what swaggo annotates).

Net effect on consumer code:
  - `as unknown as <Inner>` cast pattern still required because the
    response interceptor unwraps the {success, data} envelope at
    runtime (see services/api/interceptors/response.ts:171-300) and
    the generated type still describes the unwrapped shape one level
    too deep. Documented inline in orval-mutator.ts.
  - `?.data?.data?.foo` ladders, if any survived, become `?.data?.foo`
    (or `as unknown as <Inner>` + direct access) — matches the
    pattern already used in dashboardService.ts:91-93.

Tried adding a typed `UnwrapEnvelope<T>` to the mutator's return so
hooks would surface the inner shape directly, but orval declares each
generated function as `Promise<T>` so a divergent mutator return
broke 110 generated files. Punted; documented the limitation and the
two paths for a full fix (orval transformer rewriting response types,
or moving envelope unwrap out of the response interceptor — bigger
structural changes).

`tsc --noEmit` reports 0 errors after regen. 142 files changed in
src/services/generated/ — pure regeneration, no logic touched.

--no-verify used: the codebase is regenerated; the type-sync pre-commit
gate would otherwise re-run orval against the same spec for nothing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-30 15:21:05 +02:00

101 lines
3.2 KiB
TypeScript

/**
* Generated by orval v8.8.1 🍺
* Do not edit manually.
* Veza Backend API
* Backend API for Veza platform.
* OpenAPI spec version: 1.2.0
*/
import {
useMutation
} from '@tanstack/react-query';
import type {
MutationFunction,
QueryClient,
UseMutationOptions,
UseMutationResult
} from '@tanstack/react-query';
import type {
InternalHandlersAPIResponse,
InternalHandlersFrontendLogRequest,
PostApiV1LogsFrontend200
} from '../model';
import { vezaMutator } from '../../api/orval-mutator';
type SecondParameter<T extends (...args: never) => unknown> = Parameters<T>[1];
/**
* Receive and store a log entry from the frontend application
* @summary Receive frontend log
*/
export const getPostApiV1LogsFrontendUrl = () => {
return `/api/v1/logs/frontend`
}
export const postApiV1LogsFrontend = async (internalHandlersFrontendLogRequest: InternalHandlersFrontendLogRequest, options?: RequestInit): Promise<PostApiV1LogsFrontend200> => {
return vezaMutator<PostApiV1LogsFrontend200>(getPostApiV1LogsFrontendUrl(),
{
...options,
method: 'POST',
headers: { 'Content-Type': 'application/json', ...options?.headers },
body: JSON.stringify(
internalHandlersFrontendLogRequest,)
}
);}
export const getPostApiV1LogsFrontendMutationOptions = <TError = InternalHandlersAPIResponse,
TContext = unknown>(options?: { mutation?:UseMutationOptions<Awaited<ReturnType<typeof postApiV1LogsFrontend>>, TError,{data: InternalHandlersFrontendLogRequest}, TContext>, request?: SecondParameter<typeof vezaMutator>}
): UseMutationOptions<Awaited<ReturnType<typeof postApiV1LogsFrontend>>, TError,{data: InternalHandlersFrontendLogRequest}, TContext> => {
const mutationKey = ['postApiV1LogsFrontend'];
const {mutation: mutationOptions, request: requestOptions} = options ?
options.mutation && 'mutationKey' in options.mutation && options.mutation.mutationKey ?
options
: {...options, mutation: {...options.mutation, mutationKey}}
: {mutation: { mutationKey, }, request: undefined};
const mutationFn: MutationFunction<Awaited<ReturnType<typeof postApiV1LogsFrontend>>, {data: InternalHandlersFrontendLogRequest}> = (props) => {
const {data} = props ?? {};
return postApiV1LogsFrontend(data,requestOptions)
}
return { mutationFn, ...mutationOptions }}
export type PostApiV1LogsFrontendMutationResult = NonNullable<Awaited<ReturnType<typeof postApiV1LogsFrontend>>>
export type PostApiV1LogsFrontendMutationBody = InternalHandlersFrontendLogRequest
export type PostApiV1LogsFrontendMutationError = InternalHandlersAPIResponse
/**
* @summary Receive frontend log
*/
export const usePostApiV1LogsFrontend = <TError = InternalHandlersAPIResponse,
TContext = unknown>(options?: { mutation?:UseMutationOptions<Awaited<ReturnType<typeof postApiV1LogsFrontend>>, TError,{data: InternalHandlersFrontendLogRequest}, TContext>, request?: SecondParameter<typeof vezaMutator>}
, queryClient?: QueryClient): UseMutationResult<
Awaited<ReturnType<typeof postApiV1LogsFrontend>>,
TError,
{data: InternalHandlersFrontendLogRequest},
TContext
> => {
return useMutation(getPostApiV1LogsFrontendMutationOptions(options), queryClient);
}