16 posts tagged with "Ruby"

APIMatic CodeGen has now added support to configure the default Faraday connection with available Faraday adapters in Ruby SDKs.

We are now dropping support for Ruby version 2.5 in Ruby SDKs. Ruby 2.5 hit EOL status on 2021-03-31 as per the official source. As a result of dropping Ruby 2.5, we are now able to relax version constraints on some of the Ruby SDKs dependencies.

We've fixed an issue in SDKs where HTTP redirections were not being handled properly. Please generate new SDKs to receive the fixes.

We've updated our SDKs that use OAuth 2 Client Credential Flow to enable automatic re-authorization of the client when the OAuth token is expired.

We have added a new CodeGen setting that allows you to specify a list of words that Code Generation will not split when converting identifiers from API specification to language-specific identifiers. This is useful for declaring brand names such as APIMatic.

E.g. if you provide the words apimatic and vmware in your the list, APIMaticandvmWare becomes ApimaticAndVmware or apimatic_and_vmware, depending on the place of use.

We have added support for adding contact information of the organization maintaining the API in our API editor.

Our Android, .Net, Go, Java, NodeJS, PHP, Python and Ruby SDKs now allow skipping verification of SSL certificates. To do this enable the CodeGen Setting Allow Skipping Certificate Verification and then set the corresponding configuration variable in the respective SDK.

We have added a new CodeGen setting to allow disabling linting in our SDKs. If you would like to benefit from this feature then please enable the setting and generate your SDKs again.

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.

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.