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
Up until the most recent v6 release of the c# Recommend client, it was possible to use type arguments with the GET methods, in a similar fashion to the search client, e.g:
However, with v7 there seem to only be non-generic GET methods, e.g:
_recommendClient.GetRecommendationsAsync()
_recommendClient.CustomGetAsync()
It feels like the v7 recommend client isn't finished yet? Is that correct, or is this currently overlooked behaviour, as it introduces some serious breaking changes if it's no longer possible to retrieve strongly typed records from the recommend requests?
Client
Recommend
Version
7.2.4
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
Hello, this is the expected behavior as the only thing changing between all functions is the body, they are all requesting the same endpoint.
The argument to GetRecommendationsAsync is still strongly typed, you can find an example in the documentation snippet.
I agree that the usage is not as straight forward as v6, but v7 reflects more closely the underlying api, and all the functionalities are still there.
Description
Up until the most recent v6 release of the c# Recommend client, it was possible to use type arguments with the GET methods, in a similar fashion to the search client, e.g:
_recommendClient.GetRecommendationsAsync()
_recommendClient.GetRelatedProductsAsync()
However, with v7 there seem to only be non-generic GET methods, e.g:
_recommendClient.GetRecommendationsAsync()
_recommendClient.CustomGetAsync()
It feels like the v7 recommend client isn't finished yet? Is that correct, or is this currently overlooked behaviour, as it introduces some serious breaking changes if it's no longer possible to retrieve strongly typed records from the recommend requests?
Client
Recommend
Version
7.2.4
Relevant log output
No response
The text was updated successfully, but these errors were encountered: