79 posts tagged with "Improvement"

APIMATIC's Ruby SDKs are now compliant with The Ruby Style Guide

• Ruby style guide compliance means that the Ruby code generated is guaranteed to be of high-quality.
• Ruby SDKs are written in an industry-standard code style to allow for maximum interoperability.
• Ruby SDKs can be tested for code style violation using Rubocop.

Re-generate your Ruby SDKs now for the new changes.

APIMATIC's Python SDKs are now compliant with the PEP8 Coding Style Guide

• PEP8 compliance means that the Python code generated is guaranteed to be of high-quality.
• Python SDKs are written in a industry-standard code style to allow for maximum interoperability.

Re-generate your Python SDKs now for the new changes.

APIMATIC's CSharp SDKs are now compliant with the StyleCop Coding Style Guide

• StyleCop compliance means that the CSharp code generated is guaranteed to be of high-quality.
• CSharp SDKs are written in a industry-standard code style to allow for maximum interoperability.

Re-generate your CSharp SDKs now for the new changes.

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 disallowed properties were being exported and some required properties and discriminator details were missing.

We are happy to announce that our .NET SDKs have now switched to the more stable, 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.

Improvements have been made to WSDL import by fixing minor bugs, adding new features, and improving on the existing ones in an effort to make it more compliant with the official W3C specification

We have changed the structure of the Angular SDK to break cyclic dependencies. Due to this, the following changes have been made:

• Model deserialization logic has moved out from model files.
• We have added new files ObjectMapper.js and ModelFactory.js to the SDK.
• BaseModel is now being used to assign values to model properties (when model class is directly instantiated)
• BaseController has been added to the SDK.

Please generate your SDK again to get the improved code.

Since we're always working on improving our generated SDK's, today we're announcing some major work done on the Angular.js SDK.

• Angular.js generated code is now standard compliant.
• The standard we're using is John Papa's Angular1 Style Guide.
• The linter can be run from the command-line by using the command jshint <folder-name-to-lint>.
• The configuration file for the linter will be included with the SDK from now.

Please generated your SDK again to get the standard compliant code.

We've made an improvement to how model properties are now generated in the code. The generated SDK now contains both camel case-d version of the property name and the actual property name (where applicable).
Read on to find more details about the change.

Please generate your SDK again to get the improved code.