* Update RestSharp to v108
* Add OAuth2 Application (client_credentials) authentication
* Run generators and fix typos
* Undo accidental python and rust changes
* Add documentation, fix authenticator bug, and fix user agent bug
* Fix tests
Missed some changes in the mustache templates.
Also had to update the `netcoreapp2.0` test project to `netcoreapp3.1` for compatibility with RestSharp
* Switch HttpUtility to WebUtility for compatibility
* skip oauth file generation for httpclient
* fix templates
* remove files, regenerate samples
* add reference to system.web
Co-authored-by: Jared Bates <Jared.Bates@sight-sound.com>
* Update RestSharp to v108
* Add OAuth2 Application (client_credentials) authentication
* Run generators and fix typos
* Undo accidental python and rust changes
* Add documentation, fix authenticator bug, and fix user agent bug
* Fix tests
Missed some changes in the mustache templates.
Also had to update the `netcoreapp2.0` test project to `netcoreapp3.1` for compatibility with RestSharp
* Switch HttpUtility to WebUtility for compatibility
* Perl: separate date and DateTime
- Since the json values to be returned are different for date and DateTime, they are managed separately
* Per: Enforcing Perl types to openAPI types
Perl JSON values return different types depending on the context, so look at openapi's type and modify the type.
* generate samples
* generate docs
* add perl test (json types)
* Spec regenerated with only allOf on
Sample regnerated
Fixes a bug where AnyType composed schemas omitted validations, Fixes a bug where properties in AnyType schemas were omitted, Stops storing multipleOf value in a list
Adds required variable info to AnyType classes
Samples regenerated
Turns all unit tests back on
* Samples regenerated
* Docs and models regenerated
* Added port definition to uriBuilder, since it was ignored before and couldn't be set even by supplying a custom client
* generated samples
* update samples
Co-authored-by: Matthias Lewen-Rieger | PROSPER X GmbH <matthias.lewen-rieger@prosper-x.de>
Co-authored-by: William Cheng <wing328hk@gmail.com>
Commit 1735ab9d27 added changes to set the `jakarta_annotation_version`.
I've recently noticed that when using retrofit2 library, the project builds fine with Maven but fails with Gradle.
The build fails due to `Could not get unknown property 'jakarta_annotation_version' for object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler`.
Digging into this, in the generated `build.gradle` the `jakarta_annotation_version` is never set.
Upon closer inspection, aforementioned commit seems to indeed set it differently for the Maven build configuration than the Gradle build configuration (same for SBT configuration) for that matter.
The issue is that due to human error the `jakarta_annotation_version` line is added within the `{{#usePlayWS}}` block, meaning it won't be generated when `usePlayWS` is false, even though it should.
This commit changes this to always generate it.
* add streaming option to r client
* support callback function to process data stream
* add stream test, minor bug fixes
* fix api client
* return void earlier if streaming, add tests
* [BUGFIX] model_generic.mustache: Display property name instead of its value, when throwing InvalidArgumentExeption() for values not respecting a given pattern
* [AUTOGENERATED] Generated files
