* fix circleci test failures
* trigger test
* update circleici pom.xml
* rearrange test
* comment out tests
* fix test
* comment out python-prior
* comment out test
* fix import
* comment out tests
* Implement WARN messages for ineffective schema validation constraints
* Implement tests String, Number, Object schema validations
* Implement HashSet to store Validations for different types
* Revert Validation Helper functions; Add Test cases for Any and Boolean
* Implement Unit Test for Array with inffective schema validations
* Reformat Code; Optimize Imports
* Add assertions to ineffective validation tests
* Add Test case for Null Schema Validations
* Adjust log level and message
* Merge commit ... into issue-6491
---------
Co-authored-by: Chidu Nadig <chidu.nadig@gmail.com>
* update openapi-generator dep
* update dep, fix tests with new spec
* update kotlin version
* revert cafferine version
* add back testng version and scope
* Add support for Angular v15
Support for:
- rxjs 7.5.5
- ngPackagr 15.0.2
- zonejs 0.11.5
- typescript >=4.8.2 and <4.10.0
Note that tsTickle is not added to the dependencies when generating for
Angular 15, as:
- it is not a real dependency
- tsTickle is compatible with any of the TypeScript versions that
Angular 15 supports.
* Generate samples for Angular v15
- typescript-angular-v15-provided-in-root
- typescript-angular-v15-query-param-object-format
* Drop sample typescript-angular-v15-query-param-object-format
* Fix typo
* Add tests for sample
Use credentials instead of api_key to avoid deprecation warnings when
initialising ConfigurationParameters.
* Update samples/client/petstore/typescript-angular-v15-provided-in-root/package.json
* Fix tests by removing context initialisation
Also updated the test dependencies.
Co-authored-by: Esteban Gehring <esteban.gehring@gmail.com>
* clean up shippable ci related config and files
* comment out closeAndReleaseRepository
* Revert "comment out closeAndReleaseRepository"
This reverts commit 5a76e403b1.
* remove closeAndReleaseRepository
* update echo to newer version
* add github workflow
* minor fix
* add install
* go get
* install middleware
* test go api server
* trigger build
* test go-api-server
* Revert "test go api server"
This reverts commit 42f24e578f.
* Revert "Revert "test go api server""
This reverts commit 7ce773275b.
* update samples
* test go gin in github workflow
* go install
* Revert "go install"
This reverts commit ec099b48c1.
* Revert "test go gin in github workflow"
This reverts commit 120516856e.
* remove go api, echo server tests
* fix: remove option supportPython2.
[python-flask][python-aiohttp][python-blueplanet]
* fix: update samples
* test only python servers
* fix(tests): downgrade pytest version to ensure compatibility with python3.6 [python-flask][python-aiohttp]
* Revert "fix(tests): downgrade pytest version to ensure compatibility with python3.6 [python-flask][python-aiohttp]"
This reverts commit 9f47db2f87.
* test in circlei
* run commands directly
* test in node 1
* update makefile
* fix Makefile
* fix test
* revert some changes, remove python server tests from travis
Co-authored-by: Kevin Bannier <kevinbannier1@gmail.com>
* [Ruby] Use Ruby autoload to lower memory usage and load times
Fixes#12648
Requiring all models up front can be very expensive in both time and
memory if there are many models. In an example client with 6000 models,
this would consume nearly 400MB of memory and take about 7 seconds to
load. This is mostly unnecessary as most users of the client library
will only actually use a small percentage of the library.
The changes in this commit use Ruby's autoload capability to defer the
loading until the constant is actually used. In that same example client
with 6000 models, when initially requiring the library, the memory
usage dropped to ~20MB and loaded in 0.3 seconds. As the constants are
loaded on-demand, the memory would increase towards that 400MB ceiling,
but if only a few constants are actually used, then memory will never
actually hit that ceiling.
An additional side effect of using Ruby's autoload is that the order of
declaring the constants is not important, as Ruby will naturally load
them in the correct order when they are needed. Thus, this commit obviates
PR #9103 and fixes#4690.
* add option to use autoload in ruby client
* test ruby clients only
* add tests
* update samples
* Revert "test ruby clients only"
This reverts commit 0aaf71cd4c.
* update doc
Co-authored-by: Jason Frey <fryguy9@gmail.com>