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
{{ message }}
This repository has been archived by the owner on Jul 25, 2019. It is now read-only.
We're making API calls to get a list of articles. Article structure is defined in the REST call documentation but why doesn't the C# API (or other language APIs) provide data models that we can simply deserialize with NewtonSoft (same library UserVoice uses)?
var articles = JsonConvert.Deserialize<List<UserVoiceArticle>>(json);
The alternative is to have 10,000,000 (if you guys are successful) developers re-implement these classes based on the REST documentation. JSON is schema-free which is fine, but UserVoice is definitely aware of its response payload structures and should provide those models in each of its SDKs.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We're making API calls to get a list of articles. Article structure is defined in the REST call documentation but why doesn't the C# API (or other language APIs) provide data models that we can simply deserialize with NewtonSoft (same library UserVoice uses)?
var articles = JsonConvert.Deserialize<List<UserVoiceArticle>>(json);
The alternative is to have 10,000,000 (if you guys are successful) developers re-implement these classes based on the REST documentation. JSON is schema-free which is fine, but UserVoice is definitely aware of its response payload structures and should provide those models in each of its SDKs.
The text was updated successfully, but these errors were encountered: