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
If error responses do not declare a content type, then success responses can be typed as undefined. Issue creation #86: Issue #2350 opened by dwjohnston
13s
13s
Error when the response has a field name called "summary" Issue creation #85: Issue #2349 opened by kyawsiesein
12s
12s
Hope to export a Client that only exposes queryOptions Issue creation #84: Issue #2346 opened by faner11
12s
12s
openapi-react-query Feature Request: Expose useQueryClient Issue creation #83: Issue #2345 opened by ataylorme
11s
11s
API calls do not use the content-type Issue creation #82: Issue #2344 opened by aaronbeall
13s
13s
Error type incorrectly inferred Issue creation #81: Issue #2343 opened by CynicalBusiness
11s
11s
cjs format error in openapi-typescript@7.8.0 Issue creation #80: Issue #2342 opened by liangskyli
13s
13s
Incorrect TypeScript generated when using true TS enums and top-level type exports without prefix Issue creation #79: Issue #2341 opened by conTroll
14s
14s
initialPageParam in useInfiniteQuery shouldn't default to zero Issue creation #78: Issue #2340 opened by mevansAI
9s
9s
Excess parameters allowed in createClient endpoint calls Issue creation #77: Issue #2329 opened by GaddiSunshine
14s
14s
When sending multipart/form-data, the Content-Length header is set incorrectly due to the use of new Request Issue creation #76: Issue #2328 opened by Cigan12
13s
13s
Support for infiniteQueryOptions and useSuspenseInfiniteQuery Issue creation #75: Issue #2326 opened by Valatka
14s
14s
query parameters with default value are marked as optional Issue creation #74: Issue #2319 opened by domantas-simplex
8s
8s
Name of schema generated as type value when using oneOf Issue creation #73: Issue #2318 opened by raduinsuretech
9s
9s
Propagate request's response to be able to read status codes, and more Issue creation #72: Issue #2317 opened by konsalex
12s
12s
Differentiate between success and error for empty responses Issue creation #71: Issue #2291 opened by cbodin
12s
12s
useMutation type constraint error: paths missing index signature (Record<string, Record<HttpMethod, {}>>) Issue creation #70: Issue #2267 opened by gromchen
15s
15s
TypeError: Cannot read properties of null (reading 'useContext') Issue creation #69: Issue #2266 opened by jean-smaug
15s
15s
Exposing directly components types Issue creation #68: Issue #2265 opened by Aschen
13s
13s
improve mutation workflow Issue creation #67: Issue #2261 opened by mplemay
12s
12s
support func argument for swr mutate Issue creation #66: Issue #2259 opened by prescottprue
9s
9s
useInfiniteQuery's select option does not infer correct type Issue creation #65: Issue #2258 opened by mpash
13s
13s
Ability to access response object in onError function Issue creation #64: Issue #2257 opened by deweve
15s
15s
Process crashes if the schemas has an object type with a key containing a % sign Issue creation #63: Issue #2251 opened by sbe-visma
13s
13s
Access Response alongside data, error, isLoading, etc. Issue creation #62: Issue #2247 opened by Arian94
12s
12s