bump up version

CHANGELOG.md

@@ -1,3 +1,9 @@
+## 0.15.0 (8.12.2014)
+
+- **new feature**: binding dynamic variable `ring.swagger.json-schema/*ignore-missing-mappings*`
+  to true will cause unknown json-schema mappings to be ignored
+- fixed #42
+
 ## 0.14.1 (11.10.2014)
 
 - support for `s/Named`

README.md

@@ -61,13 +61,19 @@ In namespace `ring.swagger.schema` there are some helpers for creating the schem
 | `(s/required-key X)`    | *required key*
 | `s/Keyword` (as a key)  | *ignored in visualizations*
 
-
-
 - Vectors, Sets and Maps can be used as containers
   - Maps are presented as Complex Types and References. Model references are resolved automatically.
   - Nested maps are transformed automatically into flat maps with generated child references
     - Nested maps can be within valid containers (as only element - heregenous schema sequences not supported by the spec)
 
+### Missing Schema elements
+
+If ring-swagger can't transform the Schemas into JSON Schemas,
+by default a `IllegalArgumentException` will be thrown. By binding
+`ring.swagger.json-schema/*ignore-missing-mappings*` to true, one
+can ingore the errors (missing schema elements will be ignored from
+the generated JSON Schema).
+
 ### Schema elements supported by `ring.swagger.json-schema-dirty`
 
 Some Schema elements are impossible to accurately describe within boundaries of JSON-Schema or Swagger spec.

project.clj

@@ -1,4 +1,4 @@
-(defproject metosin/ring-swagger "0.14.1"
+(defproject metosin/ring-swagger "0.15.0"
   :description "Swagger Spec for Ring Apps"
   :url "https://github.com/metosin/ring-swagger"
   :license {:name "Eclipse Public License"