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
In some cases, you can encounter wrongly named `requestBody` from the specs, which is due to:
61
+
In some cases, you can encounter wrongly named `requestBody` from the specs, which could be due to:
62
62
63
63
- The type is too complex/too broad to be generated. (e.g. [An object with `additionalProperties`](https://github.com/algolia/api-clients-automation/tree/main/specs/search/paths/objects/partialUpdate.yml#L24-L33))
64
-
- The body is an alias of its sub type (e.g. [A list of sub models](https://github.com/algolia/api-clients-automation/tree/main/specs/search/paths/rules/saveRules.yml#L12-L20))
64
+
- The type is an alias of its model (e.g. [A list of `model`](https://github.com/algolia/api-clients-automation/tree/main/specs/search/paths/rules/saveRules.yml#L12-L20))
65
65
66
-
The `x-codegen-request-body-name` property can be added at the root of the spec, to force the name of the generated `requestBody` property.
66
+
The [`x-codegen-request-body-name`](https://openapi-generator.tech/docs/swagger-codegen-migration/#body-parameter-name) property can be added at the root of the spec, to force the name of the generated `requestBody` property.
67
67
68
68
You can find an example of this implementation [on this PR](https://github.com/algolia/api-clients-automation/pull/896).
0 commit comments