-
Notifications
You must be signed in to change notification settings - Fork 3
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
Conversion to .net standard #4
Comments
I have a version ready for net standard: It would probably be best if it is supplied by you instead. |
If I set "DetailLevel" to "ItemReturnDescription": Returns the description, plus the ListingDesigner node and some additional information if applicable. |
@lovetofail How critical is this for you? |
|
I updated my fork. Can you create a minimal example, how I can test your issue? Beware, I went very berserk on the source to make this work. I had mainly my own usecase in focus, as I wasn't sure that my effort will have any value for anyone else as this repository seems pretty dead. |
Deserialization fails because "ListingDesigner" contained in ebay response when DetailLevelCodeType.ReturnAll or DetailLevelCodeType.ReturnDescription. Appreciate your help, I would never converted this to .NET *Update: When IncludePrefilledItemInformation is present in ProductListingDetails it makes ProductListingDetails fields default too. Code sampleprivate static void DeserializeFail(string apiToken)
} |
Hello,
is a conversion to .NET standard planned or in the works?
Would a PR accepted for that?
The text was updated successfully, but these errors were encountered: