-
Notifications
You must be signed in to change notification settings - Fork 76
/
Copy pathCHANGELOG
151 lines (100 loc) · 3 KB
/
CHANGELOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
5.4.0
-----
- Bugfix for correct typecasting of status codes for response validation.
https://github.com/pipermerriam/flex/issues/108
5.3.0
-----
- Bugfix for incorrect validation of paths. https://github.com/pipermerriam/flex/issues/106
5.2.1
-----
- Bugfix for Tornado server request object support for request validation.
5.2.0
-----
- Fix bug with uniqueness enforcement with unhashable types.
- Fix request/response validation not falling back to the "default" response.
- Fix path matching to not match parameters across slashes
5.1.0
-----
- Fix validation of `contact` to be of type `object`
5.0.0
-----
- CLI interface name changed to `swagger-flex` to avoid name collision with
Apache Flex project.
4.3.0
-----
- Support for tornado requests and response objects
4.2.1
-----
- Fix for error message from `minLength` and `maxLength` validation. See
https://github.com/pipermerriam/flex/issues/84
4.2.0
-----
- Add validators for the additionalProperties keyword from JSON-schema
4.1.0
-----
- Fix parsing and validation of Reference Objects for Responses and Parameters.
4.0.1
-----
- Remove the use of pip's internals in the setup.py file.
4.0.0
-----
- Breaking Change: Changes the implementation for how ``$ref`` values were
validated and resolved to be compliant with the json pointer spec
(RFC6901 https://tools.ietf.org/html/rfc6901).
3.5.1
-----
- Fix bug with how the keyword `default` was being validated for Parameter
Objects.
- Fix how the keyword `externalDocs` was validated on Operation and Schema
objects.
3.5.0
-----
- Add body parameter validation to api request validation.
3.4.1
-----
- Bugfix: Changed the strategy for picking an api_path when multiple regexes
match from using the length of the regex match groups, to the length of the
corresponding API path.
3.4.0
-----
- Backwards Incompatible Bugfix around how the `required` keyword for Schema
Objects is handled. Previously, it was expected to be a boolean and to apply
to the current schema. It is now correctly validated as an array of strings
that dictate which properties are required.
3.3.0
-----
- Bugfix around path matching and handling duplicate path matches for api
request/response validation.
3.1.0
-----
- Fix bug with request path matching where a path with a parameter defined at
the operation level would not be matched.
3.0.0
-----
- Remove DRF dependency.
- Remove limitation that schema properties cannot intersect with reserved words
in the schema spec.
2.8.0
-----
- Fix query parameter validation bug
2.7.0
-----
- Fix bug with binary/text type values in enum validation not being considered
equal.
2.6.0
-----
- Fix bug related to validating path parameters for api's with a basePath.
2.5.0
-----
- Implement response url validation
- Implement response header validation
2.4.0
-----
- Fix bug in api_call_validation
2.3.0
-----
- Support for DRF2 and DRF3.
2.0.0
-----
- Extends response validation to request headers.
- Extends response validation to response body.