* Added field and class level annotations
Added x-class-extra-annotation and x-field-extra-annotation for class and field level annotations per object/field
* added field and class level extra annotations to pojos
* Updated samples
* Removed duplicate line
* Updated samples
It is possible, though contrived, for a property to have both isAnyType
and isModel set. In this case, when the outer type is nullable, the Go
template expects a Nullable* type to be provided by the generator, but
it is skipped over instead. This change aligns the generator with the
template's expectations.
A recent enhancement to the template made these primitive types usable
as property names, but a small section of the template wasn't updated,
leading to compilation problems.
Obvious typo in the kotlin help description of the
`supportAndroidApiLevel25AndBelow` configuration parameter i.e.
`in oder` instead of `in order`.
Co-authored-by: Slawomir Kwasniak <slawomir.kwasniak@hensoldt-cyber.de>
For some buggy configurations, a warning is emitted indicating that for
a given request body the corresponding CodegenModel could not be found.
When this happens, some generators produce NPEs when writing out example
code. This change avoids the NPEs by providing a stub value instead.
* GetReferenceHeader for both calls of headerToCodegenParameter
* Moved dereferencing of header outside of headerToCodegenParameter
Co-authored-by: Westerlaken, H.L. (Laurens) <laurens.westerlaken@devolksbank.nl>
The generator ran into a loop when a composite schema recursively added itself. This change provides a reproducing example and fixes the issue by extending DefaultCodegen#addProperties() by an additional circuit breaker parameter.
When additionalProperties() is called with a schema instance for which the properties have already been added, the method directly returns and does not run into the loop.
Remove undefined value from header
Envoyé depuis mon iPhone.
P.S. : Ce commit est certifié sans gluten
Co-authored-by: Géry THRASIBULE <g.thrasibule@lecomptoirdespharmacies.fr>
* [Ada] New options to choose the Ada support library in client and server generated code
* new option httpSupport to choose between Curl or AWS (Ada Web Server) support
* new option openApiName to choose the package name of the OpenAPI support library
* update the templates to customize the support library
* update generated GNAT config.gpr file
* update the client petstore Ada samples
* Fix call to toLowerCase() to give a locale
* Rebuild the Ada generator documentation
In the generated java code, it is usefull to have the generated java api
use the @Deprecated annotation. This enable to leverage this annotation
at runtime to trigger specific logging for instance.
In the generated interface, use the @Deprecated annotation.
Also, in the jax-rs implementation that links the jax-rs api with the
cdi bean implementing the interface, use the
@SuppressWarnings("deprecation") annotation. This way the deprecation
warning is not shown in generated code.
One can use the interface as before: the java compiler can then tell
which implementations do implement a deprecated api, using a warning.
If the implementation itself also sets the @Deprecated annotation, then
there is no warning, unless the implementation is called at another
place in the code.
