Jens Schulze

There are some possible ways to go here. One is to create a specific middleware that checks if in the response body the error field is not empty and raises...

With the latest release ([14.3.0](https://github.com/commercetools/commercetools-sdk-java-v2/releases/tag/14.3.0)) you now have the possibility to create type safe queries.

I tried something similar with the QueryInfoProvider. But you have to fetch the CallerArgumentExpression in the wrapper method else it will not work: ``` public static void Query(Func query, [CallerArgumentExpression("query")]...

It would already help if there is a way that the analyzers capture classes implementing an interface provided by ZeroQL so libraries could implement it and read the query body...

This is an example availability for a product: ``` "availability": { "channels": { "cd724bd4-52fa-4d6d-b4b0-bb1560d70475": { "isOnStock": true, "restockableInDays": 10, "availableQuantity": 20, "version": 1, "id": "f64af276-a1ad-4eea-a8bc-89c453742a40" } } } ``` The...

Yes. It has been added today. The changes are already merged to this repository. Both fields will be available with the next release. Please see also: https://github.com/commercetools/commercetools-sdk-typescript/pull/626/files

It's not an issue of the SDK. We don't use the XmlElement annotation. The incompatibility comes from Jackson in combination with Spring Boot 3. You will have to find some...

We didn't experiment yet with virtual threads. When I remember it right the executor wasn't forwarded to the OkHttp dispatcher for backwards compatibility reasons as it potentially would have changed...

The reason for this is that the BaseMoney is an interface and it has two implementations Money and HighPrecisionMoney. The Deserializer can't distinguish them as you didn't "cast" the request...

The question is how it should look like. I didn't saw a possibility to add tags or labels to an request. So it must be added to the request name....