60 posts tagged with "New Feature"

You can now set Composer Package Name for PHP SDKs being generated.

This will affect the name generated in the composer.json file. Leaving it empty will generate the a fallback package name based on your API name.

Good news! You can now export your existing API description files to WSDL. The generated WSDL can be utilized in generating server interfaces using VS developer tools in addition to other benefits. The WSDL generated follows the WSDL 1.1 format specified at https://www.w3.org/TR/wsdl.

Now you can upload a ZIP file containing your Postman Collection file along with any Postman Environment Files. That way we will extract values for your environment variables from the Environment files and give a better output during conversions on the Transformer or when importing APIs to your Manage APIs page. Support for Postman data dump files has now been added as well.

NodeJS SDKs will now return promises in endpoint calls, as an alternative to accepting callbacks.

• We use ES6 Promises which is based on Promises/A+ and is interoperable with most Promise-based implementations.
• Callbacks are still supported (for backward-compatibility) but are now optional.

Re-generate your NodeJS SDK to get the new Promise-enabled SDK implementation now.

NodeJS SDKs can now optionally preserve additional properties returned in the response. This setting can be enabled via Settings > CodeGen Settings page in the API editor and turning on the Enable Additional Model Properties flag.

APIMatic Code Generation engine now supports polymorphic responses with the help of a discriminator field.

• 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.

Check out the Discriminator documentation to get started.

If you have a Swagger 1.2 API description file split into Resource Listing and API Declaration files, you can import/convert it using a ZIP file. Previously, such API description file could only be converted/imported by providing the Resource Listing file via a URL where all API Declaration files were located relative to this URL.

Multiple formats are now supported for Array serialisation in form and query parameters. Formats supported include UnIndexed, Indexed, Plain, CSV, PSV, TSV.

This settings can be set using our API Blueprint CodeGen setting extension named ARRAYSERIALIZATION.

Swagger makes use of a property discriminator to support polymorphism in custom types. We have now added support for this property in our system. We also offer an extension that will allow you to specify a custom value for the discriminator to override its default value.

We've now added support for additional properties in models in the CSharp SDK. The additional properties are deserialized and stored in a dictionary inside the model.

This can be enabled via navigating to the Settings > CodeGen Settings page in the API editor and enabling the Enable Additional Model Properties flag.