Changelog

Swagger allows schema inheritance through the use of property “discriminator” in the base schema. During conversions on Transformer/ Dashboard the base type information for child schemas was not being extracted properly and this bug has now been fixed. Additionally, Open API 3.0 export has been improved by eliminating several bugs e.g. some extra unallowed properties were being exported and some required properties and discriminator details were missing.

Several minor and major bug fixes were made to the Postman (1.0, 2.0) import and export. These fixes were relevant to issues in parsing request URLs containing environment variables and in parsing port information in Postman 2.0.

We are excited to announce the latest addition to our long list of supported platforms. Our C# section now has a new template for a .NET Standad library in addition to the already supported PCL and UWP templates. This library targets .Net Standard 1.3.

We are happy to anounce that our .NET SDKs have now switched to the stabler, frequently updated and regularly maintained native HttpClient found in the System.Net.Http Assembly.

Our CSharp .NET SDKs have been updated to use the 10.0.3 version of the Newtonsoft Json.Net utility. This comes with numerous new features, bug fixes, wider support and increased stability.

Usage of discriminators is already supported by our code generation engine. We are happy to announce that now support for using discriminators has also been added to AngularJS SDK.

• Discriminator is a field that is used to differentiate between a parent model and models that inherit from it.
• The response is deserialized into the parent model or one of its child classes by inspecting the discriminator field’s value in the response.
• Using a discriminator field, you can build leaner models by not having to build unions of fields needed by a polymorphic response.

Please generate your SDK again if you want to use this feature.

There was a problem with the datetime implementation in AngularJS. Date/datetime strings were not correctly converted into objects. Instead, strings were being sent and received within the SDK. This problem has now been fixed.

Please generate your SDK again to get this fix.

There was a bug in the AngularJS SDK in sending complex types (models) as Form and Body Parameters.

In cases of endpoints which accept model instances as form/body parameters, models were not being serialized properly before making the endpoint call. This resulted in camel-cased field values being passed, disregarding the correct API names.

This behavior has now been fixed. Please generate your SDK again to get the fix.

OAuth 2.0 support was recently added to the API Editor and Code Generation engine. Now the support is added to Transformer as well as import/export in the Dashboard.

There was a bug in the Node.js SDK in sending complex types (models) as Form Parameters.

In cases of endpoints which accept model instances as form parameters, models were not being serialized properly before making the endpoint call. This resulted in camel-cased field values being passed, disregarding the correct API names.

This behavior has now been fixed. Please generate your SDK again to get the fix.