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
Better compatibility for "required" vs. "nullable" (#230)
* Added support for UNSET values and better differentiation between required and nullable.
* Models to_dict methods will not include any values which are UNSET
Co-authored-by: Ethan Mann <emann@triaxtec.com>
Co-authored-by: Dylan Anthony <danthony@triaxtec.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## 0.7.0 - Unreleased
9
9
10
+
### Breaking Changes
11
+
12
+
- Any request/response field that is not `required` and wasn't specified is now set to `UNSET` instead of `None`.
13
+
- Values that are `UNSET` will not be sent along in API calls
14
+
10
15
### Additions
11
16
12
17
- Added a `--custom-template-path` option for providing custom jinja2 templates (#231 - Thanks @erichulburd!).
18
+
- Better compatibility for "required" (whether or not the field must be included) and "nullable" (whether or not the field can be null) (#205 & #208). Thanks @bowenwr & @emannguitar!
0 commit comments