30 posts tagged with "Bug Fix"

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.

The WADL imports did not parse the Parameter style information correctly which has now been fixed.

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.

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.

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

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.

Object Instantiation in Custom Types files have now been improved. Only those properties (of the object) that are set in client code will be initialized and instantiated in the SDK. This will prevent any property from being undefined

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.

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.

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.