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
@@ -140,13 +141,19 @@ You can take a look at the implementation over all clients, [in this pull reques
140
141
141
142
Every methods of every clients provide a parameter that does not exist in the REST API, called `requestOptions`.
142
143
143
-
This parameter **must** be the last parameter of a method, and allow a user to override/merge additional `query parameters` or `headers` with the transporter ones.
144
+
This parameter MUST be the last parameter of a method, and allow a user to override/merge additional `query parameters` or `headers` with the transporter ones.
144
145
145
146
### Requesters
146
147
147
-
The requester needs to be configurable and capable to be overwriten to use a user defined requester.
148
+
The requester needs to be configurable and capable to be overwritten to use a user defined requester.
148
149
The default requester must be the classic HTTP requester, and it's possible to provide other alternatives like an [Echo Requester](https://github.com/algolia/api-clients-automation/blob/main/clients/algoliasearch-client-javascript/packages/client-common/src/createEchoRequester.ts) that just send the request back.
149
150
150
151
### Logger
151
152
152
-
> TODO: informations
153
+
> TODO: information
154
+
155
+
### Generated file banner
156
+
157
+
The banner SHOULD be added at the very top of every generated files, to avoid confusion for our users, but also redirect them to the `api-clients-automation` monorepo, where the contribution happens.
158
+
159
+
To do so, a `generationBanner` variable is available on every `mustache` templates, see [the initial implementation](https://github.com/algolia/api-clients-automation/pull/816) for more context.
0 commit comments