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
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -316,15 +316,13 @@ One can configure Ring-Swagger by providing options to `api-middleware` for key
316
316
317
317
### Api Validation
318
318
319
-
To ensure that your API is valid, one can call `compojure.api.swagger/validate. It takes the api (the ring handler returned by `api` or `defapi`) as an parameter and returns the api of throws an Exception. The validation does the following:
319
+
To ensure that your API is valid, one can call `compojure.api.swagger/validate`. It takes the api (the ring handler returned by `api` or `defapi`) as an parameter and returns the api of throws an Exception. The validation does the following:
320
320
321
321
1. if the api is not an swagger api (does not the `swagger-docs` mounted) and compiles, it's valid
322
322
2. if the api is an swagger api (does have the `swagger-docs` mounted):
323
323
- Ring Swagger is called to verify that all Schemas can be transformed to Swagger JSON Schemas
324
324
- the swagger-spec endpoint is called with 200 responses status
325
325
326
-
**TODO**: optionally [validate](https://github.com/metosin/compojure-api/wiki/Validating-the-Swagger-SPEC) the swagger spec itself againt the JSON Schema.
0 commit comments