-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Adding Dictionarry<sting, sting> to Respone #26
Comments
Do you have a specific use-case in mind? I'd prefer having them as fields, if it is known that the response will have them. |
For properties, we didn't considered yet, but are awailabe through the API. To prevent s.th. lilke in #25 (at least parcially) |
If these properties are implemened in the following release, the existing code would break if they update the dependency (or if it's a patch/minor release, if they re-install the dependeny). I'd just prefer to implement these things correctly in the first place. |
Hay Nikeee what do you think about adding a
Dictionarry<sting, sting>
(orIReadOnlyList<KeyValuePair<string, string>>
) to the respone class for all respone-parameters that couln't be deserialized?The text was updated successfully, but these errors were encountered: