You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,9 +17,9 @@ The exports can be accessed as follows:
17
17
- The `customInstance` used to make calls is exported in the case where the exported API doesn't allow certain features.
18
18
-*All* the exported types are only exported from here (limited by the output of orval but you should import types separately with `import type {} from ''` regardless).
19
19
20
-
### From the subEntry points, the `react-query` exports can be imported.
20
+
### From the sub-entry points, the `react-query` exports can be imported.
21
21
22
-
This will be the standard output of `Orval` with `react-query` These will be the `x-semantic-name` fields specified in the OpenAPI. In addition the hooks will of course be prefixed by `use` and converted to `camelCase`. Each `useQuery` hook will also have a `get${camelCase(operationId)}` function that takes the same request params and body to generate a query key.
22
+
This will be the standard output of `Orval` with `react-query` These will be the `x-semantic-name` fields specified in the OpenAPI. In addition the hooks will of course be prefixed by `use` and converted to `camelCase`. Each `useQuery` hook will also have a `get${camelCase(operationId)}` function that takes the same request params and body to generate a query key. Additionally, suspense queries are generated for `<Suspense></Suspense>` boundaries.
0 commit comments