You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My target OpenAPI endpoint gives an error upon receiving null values - total garbage, I know.
Use Case:
Currently this is the code, that I need to invoke to stop null serialization on my generated OpenAPI code:
Destinationdestination;
ApiClientapiClient = newApiClient(createRestTemplate(destination));
apiClient.setBasePath(destination.getUri().toString()); // argsl... (see side-issue)newDefaultApi(apiClient); // my service class
Please provide a convenient way to customize (de)serialization options on ApiClient or the generated Service class respectively.
It looks like the easiest option would be to expose some existing private methods on ApiClient as protected, such that I can overload them upon class instantiation.
Side issue:
When instantiating the ApiClient myself the basePath will not be overwritten by default. Independent whether I use the Destination-based or RestTemplate-based constructor.
Scenario:
null
values - total garbage, I know.Use Case:
with
Feature request:
ApiClient
or the generated Service class respectively.ApiClient
as protected, such that I can overload them upon class instantiation.Side issue:
ApiClient
myself thebasePath
will not be overwritten by default. Independent whether I use theDestination
-based orRestTemplate
-based constructor.cloud-sdk-java/datamodel/openapi/openapi-core/src/main/java/com/sap/cloud/sdk/services/openapi/apiclient/ApiClient.java
Line 108 in a6a3ec9
The text was updated successfully, but these errors were encountered: