* python: remove non-async code path from the aiohttp generator
This removes all the non-async code from the aiohttp generator:
* all the methods that should be asynchronous are marked as `async`
* the `async_req` parameter is gone; calls are directly awaitables now
* the async calls into a thread pool are gone and the thread pool is
gone too (now useless)
Closes: #15824Closes: #5539
Related: #763
Related: #3696
* Fix empty line
* remove more
* Autosets the parameters with the only value specified as enum if the parameter is also marked as required
* Autosets the parameters with the only value specified as enum if the parameter is also marked as required
* Autosets the parameters with the only value specified as enum if the parameter is also marked as required for Java default client.
* Autosets the parameters with the only value specified as enum if the parameter is also marked as required for Java default client.
* Autosets the parameters with the only value specified as enum if the parameter is also marked as required for Java default client.
* Autosets the parameters with the only value specified as enum if the parameter is also marked as required for Java default client.
* spec for recommend test
* add ValidateTask test for custom defined tasks
* add ValidateTask test for recommend option
* ValidateTask recommend default value is true
* [Go] return errors that happen while unmarshalling objects
* Update model samples
* More updates to samples
* Update failing Go store API test to match the one that passes
* add nullable case to spring test spec
* generate samples for changed spring input
* add nullable case to general test spec
* generate samples for changed general input
* generate samples again
* generates samples again
* re-build from new sources, generates samples again
The added option removes the wrapper part of build.gradle, enabling the generated project to be used as a sub project. The same option from kotlin client was used as reference for this change.
This patch fixes two issues with the Resteasy generated client code.
The first is the usage of a deprecated method, getFormData. The fix for
this issue was originally conceived by @peter-seitz.
The second issue was a problem in how the Content-Disposition header was
being constructed. If we had a file named "test.txt" and were uploading
it to a field named "myFile", the Content-Disposition header should look
like
Content-Disposition: form-data; name="myFile"
Instead, the code was using the file's name (rather than the field name)
in the name directive and the header looked like
Content-Disposition: form-data; name="test.txt"
The Content-Disposition header can take an optional directive, filename,
but I have not included that here as that directive is mostly useful for
file downloads and not uploads.
