* Make connection failures visible in Ruby SDK
The underlying HTTP library, Typhoeus, requires you to be explicit about
error handling. Unfortunately, this also means that we can't assume that
`response.success?` will be false only when the HTTP status code is not
a 200; it could also be false when the request fails (timeouts, TLS
verification issues, etc.). This commit adds explicit error handling for
these cases.
* Update samples
* python: Let logging format messages on demand
* python: Use six more
* python: Remove unused imports
* python: flake8 fixes
* python: Make examples compatible with Python 3
* python: Spelling fixes
Updated Tizen Client Codegen to remove calls to obsolete/deprecated system APIs.
The new templates are based on json-glib and libcurl.
The produced code also contains scripts for auto-generation of the documentation of the produced client library using Doxygen.
Included test cases for Petstore in /samples/client/petstore/tizen/PetStoreTest/
Signed-off-by: akhilkedia94 <akhil.kedia@samsung.com>
* Changes due to changes in Angular's http module.
* Added link to issue re Headers clone. Removed use-strict since its emitted by default from TypeScript 1.8 on.
* Added missing import for ResponseContentType.
* Added null check fix for Angular http issue.
* Updated package.json and typings
Signed-off-by: Sebastian Haas <sebastian@haas.tech>
This is useful when differentiating different error responses. Example:
if let e = error {
switch e {
case ErrorResponse.Error(400, _, _): responseLabel.text = "Unknown error"
case ErrorResponse.Error(403, _, _): responseLabel.text = "Not logged in"
default: responseLabel.text = "\(e)"
}
}
The existing error is straight from Alamofire and only includes the HTTP
status code in the body of the message (not broken out as a separate value).
It also does not include the response body, which may be useful.
* Enabling knowledge of inputSpec path for custom generators
* Enabling knowledge of inputSpec path for custom generators
* Enabling direct use of "inputSpec" property in templates
* Fixing spaces
* uncommented server.port property in application.mustache template and set it to serverPort value parsed from spec file
* update Petstore sample for Spring MVC and Boot
The mustache templates for the other Java clients (e.g
Java/api.mustache) use 3 curly brackets around the path variable
so the path is not escaped. Make the okhttp-gson template
consistent with them.
* change api and ApiClient to return cancellable NSURLSessionTasks instead of NSNumber
* define a configuration protocol for custom configurations, which can be passed to api clients instead of a global configuration, provide a default implementation with a singleton option
* integrate a workaround for a current JSONModel concurrency bug
* update to new ISO8601 pod
* add missing call to super
* integrate new templates into codegen
* updates documentation templates
* updates petstore objc generated code
* fixes objc client tests
