Skip to content

Actions: openapi-ts/openapi-typescript

Actions

Issue creation

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
issue.yml
138 workflow runs
138 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
Question: Can we leverage paths’ per-status response types to narrow data/error after branching? Issue creation #111: Issue #2392 opened by hajiung25
10s
10s
implement getQueryOptions at openapi-react-query Issue creation #110: Issue #2389 opened by barmaglot92
12s
12s
Deeply-nested arrays/objects aren’t supported in query params Issue creation #109: Issue #2387 opened by lubomirblazekcz
10s
10s
openapi-react-query: Accessing http status code Issue creation #108: Issue #2383 opened by aidan-rypens
11s
11s
Incorrect processing of requests with text/plain body Issue creation #107: Issue #2382 opened by cyberbobs
10s
10s
Incorrect typescript schema when using anyOf with properties Issue creation #106: Issue #2380 opened by joundy
10s
10s
oneOf for multiple error response types leads to invalid .ts file Issue creation #105: Issue #2379 opened by srsudar
10s
10s
Don't skip onResponse middleware when onRequest returns a Response object Issue creation #104: Issue #2378 opened by jkjustjoshing
11s
11s
$api.queryOptions query does not return queryClient.fetchQuery promise if used with useSuspenseQuery Issue creation #103: Issue #2377 opened by longzheng
14s
14s
Endpoint parsing error when the parameter is an empty string. Issue creation #102: Issue #2376 opened by pstachula-dev
13s
13s
Support --type-mappings flag Issue creation #101: Issue #2373 opened by thibautcornolti
15s
15s
Bug Report: Response["error"] does not type all thrown errors (middleware/fetch errors missing) Issue creation #100: Issue #2372 opened by Mathieu-COSYNS
12s
12s
Add support for JSON Schema examples keyword on Schema objects Issue creation #99: Issue #2371 opened by cmlee-accelins
14s
14s
Optional route params not recognised Issue creation #98: Issue #2369 opened by Akxe
7s
7s
Wrapper for useSWRMutation Issue creation #97: Issue #2367 opened by jkjustjoshing
12s
12s
Generate as const Enum-like Objects Alongside String Unions Issue creation #96: Issue #2366 opened by naseemkullah
8s
8s
Parameters storage is not fulfilled by parameters provided in ApiOperation Issue creation #95: Issue #2364 opened by spamshaker
14s
14s
incorrectly sent "Content-Length": "" Issue creation #94: Issue #2363 opened by Lodimup
7s
7s
$ref objects in query params aren't spread onto type Issue creation #93: Issue #2361 opened by aeharding
13s
13s
Types do not narrow by response code correctly. Issue creation #92: Issue #2360 opened by dwjohnston
9s
9s
Issue when using queryKey in queryOptions parameter of useQuery Issue creation #91: Issue #2359 opened by alxthm
11s
11s
Patch brace-expansion vulnerability Issue creation #90: Issue #2356 opened by tarngerine
9s
9s
@tanstack/react-query 5.80.x breaks useInfiniteQuery inference Issue creation #89: Issue #2355 opened by daviduzumeri
12s
12s
Options parameter is missing in useMutation Issue creation #88: Issue #2354 opened by mnlfischer
14s
14s
useInfiniteQuery should support dynamic pagination parameter location Issue creation #87: Issue #2352 opened by DevSnap
18s
18s