Changelog

Jan 10, 2018

Support for Nullable Properties Added to Transformer

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.


Jan 1, 2018

Support for Validation Keywords Added In Transformer

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.


Dec 15, 2017

Model Serialization Fixes for Ruby

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.


Dec 13, 2017

Array Serialization Bug Fix in Python

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.


Dec 13, 2017

Datetime Bug Fix in PHP

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.


Dec 6, 2017

Default Environment Selection Bug Fix in Angular

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.


Dec 6, 2017

Default Environment Selection Bug Fix in Node

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.


Nov 29, 2017

Multiple Datetime Formats in PHP

We have now added support for multiple datetime formats in our PHP SDKs. The following formats are supported:

  • RFC1123 Datetime: Mon, 15 Jun 2009 20:45:30 GMT
  • RFC3339 Datetime: 2016-03-13T12:52:32.123Z
  • Unix Timestamp: 1480809600


Oct 31, 2017

OAuth2 bug fix for Python

There was a bug in Python SDKs which were using OAuth2.

  • When updating the OAuth token, the compiler was trying to set the expiry time by adding an 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.


Oct 31, 2017

Multiple bug fixes for Ruby

There was a bug in Ruby SDKs which were using OAuth2.

  • When updating the OAuth token, the compiler was trying to set the expiry time by adding an int and a string.

Besides this, there were a couple of edge cases that allowed Ruby SDKs to be generated, and even the gem to be built and installed, but the code would not execute because of the following reasons:

  • require statements in the base file were not being split into multiple lines correctly. This splitting is done to ensure compliance with The Ruby Style Guide
  • New line characters in the descriptions for models/enums/exceptions were not being dealt with, causing a comment to spill over into the next line.

These bugs have now been fixed. Please regenerate your Ruby SDKs to get the fixes.