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
{{ message }}
This repository was archived by the owner on Sep 14, 2022. It is now read-only.
Copy file name to clipboardExpand all lines: docs/configuration.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
** NOTE: The following applies to swagger-node apps replying on swagger-node-runner 0.5.x and better. (ie. Any app using swagger-connect 0.1.0, swagger-express-wm 0.1.0, swagger-hapi 0.1.0, swagger-restify 0.1.0, or swagger-sails 0.1.0 - or higher versions of the same.) **
4
4
5
-
Swagger-Node application configuration is driven by the file `default.yaml` (by default) in the application's config directory. Configuration is driven by the [config](https://github.com/lorenwest/node-config/wiki/Configuration-Files) module, so reference its documentation to understand how you may set up configuration per environment and perform configuration overrides. By default, the configuration file looks something like this:
5
+
Swagger-Node application configuration is driven by the file `default.yaml` (by default) in the application's config directory. Configuration is driven by the [config](https://github.com/lorenwest/node-config/wiki/Configuration-Files) module, so reference its documentation to understand how you may set up configuration per environment and perform configuration overrides. By default, the configuration file looks something like this:
6
6
7
7
```yaml
8
8
# swagger configuration file
@@ -63,7 +63,7 @@ If no pipe is explicitly declared for a path or operation, this pipe will be pla
63
63
64
64
### swaggerControllerPipe
65
65
66
-
This names the standard pipe that plays for the swagger-node controllers (declared in the swagger.yaml with the
66
+
This names the standard pipe that plays for the swagger-node controllers (declared in the swagger.yaml with the
67
67
extension `x-swagger-router-controller`). We'll look at how that's defined in a second.
68
68
69
69
### bagpipes
@@ -80,15 +80,15 @@ This configures the swagger validator (currently swagger-tools). You can turn re
80
80
81
81
#### swagger_controllers
82
82
83
-
Because this is specified as your controller pipe (in the `swaggerControllerPipe` setting above), this pipe plays for all paths and operations where you'veare specified a controller extension (`x-swagger-router-controller`).
83
+
Because this is specified as your controller pipe (in the `swaggerControllerPipe` setting above), this pipe plays for all paths and operations where you've specified a controller extension (`x-swagger-router-controller`).
84
84
85
85
The default pipe is as follows:
86
86
87
87
1. set an error handler that converts all errors to JSON
88
88
2. run the [cors](https://www.npmjs.com/package/cors) module
0 commit comments