-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TVDB Deserialization Error #111
Comments
Hey, letting you know that response45 indicates an issue with the GetSearchResultsByRemoteIdAsync method.
Testing with 253323 results in a different serialization issue (response55) which I appended to my original bug report in the upstream. |
during my testing i saw these three issues (with a small series library) var seriesClient = provider.GetService<ISeriesClient>();
// Error: Could not deserialize the response body stream as Tvdb.Sdk.Response55.
var seriesResult = await seriesClient.GetSeriesExtendedAsync(id: 253323, meta: null, @short: true); var searchClient = provider.GetService<ISearchClient>();
// Error: Could not deserialize the response body stream as Tvdb.Sdk.Response45.
var searchResult = await searchClient.GetSearchResultsByRemoteIdAsync("62702"); var episodesClient = provider.GetService<IEpisodesClient>();
// Error: Could not deserialize the response body stream as Tvdb.Sdk.Response20.
var episodesResult = await episodesClient.GetEpisodeExtendedAsync(8273932); |
I saw that in some places the plugin code, at least catches client exceptions and returns and empty or null value. So i would create an PR to do this at least for the mention code paths above. |
Hey for these 3 problems will be fixed when thetvdb/v4-api#318 is merged. |
and another one var searchClient = provider.GetService<ISearchClient>();
// Error: Could not deserialize the response body stream as Tvdb.Sdk.Response45.
var searchResult = await searchClient.GetSearchResultsByRemoteIdAsync("tt3121722");
|
Hey @crobibero, setting "generateOptionalPropertiesAsNullable": true in the nswag,json will fix all the serialization issues mentioned in here. |
@scampower3 thank you for looking into this further, I've published |
#106 (comment)
#106 (comment)
Fixes will need to be made upstream
The text was updated successfully, but these errors were encountered: