Skip to main content

30 posts tagged with "bug fix"

View All Tags

OpenAPI Fix for HTTP Bearer Authentication

路 One min read

We have released a fix for HTTP Bearer authentication type in our OpenAPI import/transformation which was previously treating JWT as the default bearer authentication type. However, this will no longer be the case unless the bearerFormat in OpenAPI explicitly declares the format to be JWT.

Jackson Databind Vulnerability in Java SDKs

路 One min read

We've updated the version for jackson-databind, a dependency of our Java SDK, due to a vulnerability found in the previous version of the library.

We recommend that you generate and redeploy your Java SDK to get the fix.

Model Serialization Fixes for Ruby

路 One min read

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.

Array Serialization Bug Fix in Python

路 One min read

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.

Datetime Bug Fix in PHP

路 One min read

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.

Default Environment Selection Bug Fix in Angular

路 One min read

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.

Default Environment Selection Bug Fix in Node

路 One min read

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.

OAuth2 bug fix for Python

路 One min read

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.

Multiple bug fixes for Ruby

路 One min read

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.

Discriminator Usage Fixed in Java and Android

路 One min read

There was a bug where the Discriminator field was not being set by default.

When creating an instance of a model that inherited from another model, the discriminator field was not assigned a default value.

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

Postman Import/Export Bug Fixes Released

路 One min read

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.

Datetime Fixes in AngularJS

路 One min read

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.

Model Serialization Fixed

路 One min read

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.

Model Serialization (for Form Parameters) Fixed

路 One min read

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.

Datetime Fixes in Node.js

路 One min read

There was a problem with the datetime implementation in Node.js. 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.

Optional Model Field Deserialization Issue

路 One min read

There was an issue in code generation for PHP SDKs where the model classes (custom types) had fields with incorrect PHP typehints. This lead to the JsonMapper mapping responses incorrectly to models during deserialization. However, this only occurred when a model had fields that were described as optional in the API description and no default value was provided.

Re-generate your PHP SDK to get the fix.

Multiple Bug Fixes for Node SDK

路 2 min read

Multiple bugs were identified and fixed for Node SDK. A summary of all bugs is given below with some details about each:

  • There was a bug in printing multi-line string literals in controller files.
  • In Controller files, string encoding for headers had some issues.
  • Exception Class imports within Controllers were printed with invalid exception class names.
  • Moment.js (for Date/Datetime) import statement was not being handled properly.
  • Imports for Server.js and Environment.js file in index.js will now only be included if multiple base urls are specified in the API description.
  • Exception Class files' constructor function code has improved.
  • API Exception's constructor function code has improved.
  • Models or model properties which are being used in endpoints (such as parameters) are now being imported properly in the Controllers. Transitive imports are handled as well (if one model requires another, both are included in the controller).
  • Custom Type imports in model files have also been fixed now. If a custom type inherits from another custom type or contains an object of another custom type, that custom type is included in the model file. This import logic has been fixed.
  • Code in the Request Client file was not generating properly for Superagent client. Code for retries was being added even through retries were not enabled. This bug has been fixed.

All the above mentioned bugs have been fixed. We recommend generating Node SDK again to get all these bug fixes and minor code improvements.

Node Index File Import Bug Fix

路 One min read

There was a bug in the index file of the generated SDK. The import for configuration.js was not handled correctly. This bug was causing trouble in using the properties and functions exported from configuration.js.

You may generate your SDK again to get this bug fix.

Model Imports Bug Fix In Node

路 One min read

We encountered an error with custom types import in our Node SDK (with test cases). Custom Types which had spaces in between 2 words like Custom Type, or any special characters in their name were not being generated correctly. Causing the SDK to break.

This bug has been fixed now. Please regenerate your SDK if you encountered this bug.

Package File Fix

路 One min read

There was a bug being generated in the package.json file with Node SDKs that had no test cases. The bug was related to trailing commas being generated in the package file's dependencies. Causing the package file to not resolve dependencies. The bug has been fixed now.

Please regenerate your NodeJS SDK to get the bug fix

Error Model Deserialization Issue Fixed

路 One min read

A bug in PHP SDKs being generated lead to custom Error Exception Models not being deserialized properly from the response when an API error occurred. This was caused by an error in the unbox() function in the custom Exception class. It has now been fixed.

If you were using custom Error Exceptions, then please re-generate your PHP SDKs to get the fix.

`_httpContext` Undefined Issue Resolved

路 One min read

A logical error in the PHP SDKs being generated lead to a variable, _httpContext, being undefined in some cases. This resulted in a Fatal error when an APIException was expected to be thrown.

Please regenerate your PHP SDK to get the bug fix.

Python Circular Reference Fixed

路 One min read

A circular reference problem was fixed in the Python SDKs. This should have only existed if your API description had a DateTime property in a model.

Please regenerate your Python SDK to get the bug fix.

Ruby Syntax Error Fixed

路 One min read

An unexpected additional ')' existed in the generated Ruby code if the SDK had a Datetime property in a model. The syntax error was eliminated by removing this bracket.

Please regenerate your Ruby SDK to get the bug fix.