Our Transformer tool has been supporting HTTP Archive (HAR) format for a long time now. With the addition of new features to our APIMatic tool (e.g. support of multiple servers), there were a few updates required in our HAR parsers. In this regard, several missing features were added and some bugs were also fixed.
A property is nullable if it allows sending null (in case of JSON/YAML, etc.) or nil (in case of XML) as value. Several API description formats like Open API, RAML, etc. has support for nullable properties. Transformer now also supports this property and you can convert between different formats without losing this information.
Several API description formats like Swagger, RAML, WSDL, WADL, etc. support various kinds of validation keywords to restrict and validate instance values based on their type. Support for these validation keywords has now been added to Transformer. You can now convert between any of these formats without losing information for these keywords.
There was a bug in the implementation of the Unindexed and Plain array serialization formats in Ruby SDKs. Arrays of models were not being properly encoded as form fields for the two mentioned formats.
Additionally, a bug in the initialization of inherited models caused duplication in fields with names longer than one word.
Both these bugs have now been fixed. Please regenerate your Ruby SDKs to get this fix.
There was a bug in the implementation of the Unindexed and Plain array serialization formats in Python SDKs. Arrays of models were not being properly encoded as form fields for the two mentioned array serialization formats. The bug has now been fixed.
Please regenerate your Python SDKs to get this fix.
There was a problem in the handling of 'optional' DateTime fields in models. The issue has now been resolved.
Please regenerate your PHP SDKs to get this fix.
There was a bug with generating default environment in AngularJS configuration file. The default environment was overridden to be the PRODUCTION environment even if some other environment was chosen in the Server Configuration.
This bug has been fixed now. If you are using an API with multiple environments and encountered a problem with default environment selection before, please generate the SDK again to get the fix.
There was a bug with generating default environment in NodeJS configuration file. The default environment was overridden to be the PRODUCTION environment even if some other environment was chosen in the Server Configuration.
This bug has been fixed now. If you are using an API with multiple environments and encountered a problem with default environment selection before, please generate the SDK again to get the fix.
We have now added support for multiple datetime formats in our PHP SDKs. The following formats are supported:
Mon, 15 Jun 2009 20:45:30 GMT2016-03-13T12:52:32.123Z1480809600There was a bug in Python SDKs which were using OAuth2.
int and a string.This bug has now been fixed. Please regenerate your Python SDKs if you're using OAuth 2 to get this fix.