Swagger-parser 2.0.14 released!

Swagger-parser 2.0.14 released!

Notable Changes:

• Resolving references better handled:
  Issues: #1147 - #1177 - #1161 - #1170 - #1157 - #1165

• Fixes for Parser Options:
  Issues: #1181 - #1148 - #1158

• Different deserializing fixes:
  Issues: #1179 - #1173 - #1119 - #1145

Swagger-parser 1.0.46 released!

Swagger-parser 1.0.46 released!

Minor bug fix release:

• Fix for multiple path params in a same URI segment of a path in v1 #1169
• Fix for referenced parameter produces a validation error#1146 #1154

Swagger-parser 2.0.13 released!

Swagger-parser 2.0.13 released!

Notable Changes:

• Resolve request body examples - issue #1131 in PR #1132
• boolean enum values incorrectly deserialized - issue #1129 in PR #1130
• Fix for fully resolving map schema - issue #1125 in PR #1124
• Use SafeConstructor in snakeyaml to fix CVE - PR #1116
• Avoid prepending forward slashes when the URL already starts with a forward slash - issue #1113 in PR #1115
• Fix for Parameter.allowReserved is always null - issue #1108 in PR #1110
• Fix resolving external reference in query parameter - Issue #1094 in PR #1109
• Handle parent of parent ref - PR #1107
• Resolving Remote Ref Response with ArraySchema Ref Items - issue #1105 in PR #1106
• Remote PathItem Resolving - issue #1103 in PR #1104
• Ensure error message when "items" undefined for schema with type=array - issue #1047 in PR #1101
• Avoid wrong error message when parsing a boolean value for additionalProperties - issue #1099 in PR #1100
• Properties order lost while converting from v2 to v3 - issue #997 in PR #1093
• Fix integer type replace for number when enum values are present - issue #1090 in PR #1092
• OpenAPIV3Parser#getExtensions() not finding extensions on OSGi - issue #1003 in PR #1068

Swagger-parser 1.0.45 released!

Swagger-parser 1.0.45 released!

Minor bug fix release:

• Fix for definition type array with undefined items - issue #1047 v1 in PR #1120
• Add xml information in array models - PR #1098
• Ensure top level parameter relative references are resolved - issue #1087 in PR #1088

Swagger-parser 2.0.12 released!

Swagger-parser 2.0.12 released!

Notable Changes:

• Deserialize into MapSchema for bool additionalProperties (#1082)
• Fix for Parameter Validation Issue (#1080)
• Fix parsing of MapSchema (#1077)
• Fix set types to schemas (#1076)
• Fix NullPointerException when schema is null (#1075)
• OpenAPIV3Parser#getExtensions() not finding extensions on OSGi #1003 (#1068)
• Fix referenced parameters validation (#1065)
• Rework handling of formatted string values using getDecodedObject() (#1062)(issue #1049)

Swagger-parser 2.0.11 released! Replaces and fixes 2.0.10

Swagger-parser 2.0.11 released! Replaces and fixes 2.0.10, fixing #1053

Notable Changes:

• Fixed duplication of external reference path - issue #1040 by #1042
• Fix for Relative URLs not resolved correctly - issue #1035 by #1038
• Refine creation of Schema to fix #1032 by #1033
• Fix for default integer issues - #1029 #1015 by #1030
• Stackoverflow fix in resolveFully - refs #984 by #1028
• fix for Nested objects flattening loose lot of information ("required" for example) issue #1018 by #1026

Swagger-parser 1.0.44 released! Replaces and fixes 1.0.43

Swagger-parser 1.0.44 released! Replaces and fixes 1.0.43, fixing #1053

Minor bug fix release:

• set DeserializationUtils snake parsing log level to warning (#1044)

Please use 2.0.11 release!

Please use 2.0.11 release as it fixes #1053

Please use 1.0.44 release!

Please use 1.0.44 release as it fixes #1053

Swagger-parser 2.0.9 released!

Swagger-parser 2.0.9 released!

Notable Changes:

• Fixes remote reference parameter schemas in components (#992) - ref #983
• Fixes Swagger Parser does not evaluate references for nested map properties (#996) - ref #975
• Fixes wrong validation on default value in schemas (#1019) - ref #1015