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: docs/plugins.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,10 +5,10 @@ You can use plugins to alter how the Generator fetches data about your routes. F
5
5
Route processing is performed in six stages:
6
6
- metadata (this covers route `title`, route `description`, route `groupName`, route `groupDescription`, and authentication status (`authenticated`))
7
7
- urlParameters
8
-
- bodyParameters
9
8
- queryParameters
9
+
- headers (headers to be added to example request and response calls)
10
+
- bodyParameters
10
11
- responses
11
-
- requestHeaeers
12
12
13
13
For each stage, the Generator attempts the specified strategies to fetch data. The Generator will call of the strategies configured, progressively combining their results together before to produce the final output of that stage.
14
14
@@ -64,6 +64,9 @@ The last thing to do is to register the strategy. Strategies are registered in a
@@ -173,4 +173,4 @@ Each strategy class must implement the __invoke method with the parameters as de
173
173
174
174
Responses are _additive_. This means all the responses returned from each stage are added to the `responses` array. But note that the `ResponseCalls` strategy will only attempt to fetch a response if there are no responses with a status code of 2xx already.
175
175
176
-
- In the `requestHeaders` stage, you can return an array of headers. You may also negate existing headers by providing `false` as the header value.
176
+
- In the `headers` stage, you can return an array of headers. You may also negate existing headers by providing `false` as the header value.
0 commit comments