At this point our only option would be to revise the API version and provide an added property. Simple for us but potentially a breaking change for those mapping strongly typed variables to our output.
I may be beating a dead horse here but I am experimenting a bit with the CodeProject API creating a C# wrapper for it to (perhaps some day) be used in a Xamarin app as I am keen in learning Cross-Platform development with Xamarin.
Anyhow I have things pretty much worked out but I am curious about the FormMessages API. Both calls in that API require a ID to be passed (forum ID or thread ID) but I am at a loss as to get those ID's... Is there a way that I can retrieve those ID's through the API (I.E. am I missing something blatantly obvious) or is that still missing from the API? If so then how would I get access to those ID's?
I was afraid of that... Having to extract the forum ID's from links of the forum overview page kind of defeats the purpose of have an API. I know the API is "early beta" but it has been that way for so long that I expect it is not going to get updated any time soon.
Well... I will figure out if, and if so how I am going to deal with this.
Thanks for pointing me to the forum overview page.
Thanks. Good to hear that there is still activity on the API development as time permits. For now I decided to "mock" an API call to return a list of available forums (which will return a static ItemSummary list for now). When you get around to implementing something it should not be to difficult to replace that mock.
As for the forums at the end of an article a pointer to that should ultimately be returned through the GET V1/Articles call. That would probably mean an extra field in the ItemSummary but that way they are accesible as well.
In the my/articles api, there doesn't appear to be an element that represents the number of views or downloads. Is there a tangible reason for these to be omitted?
".45 ACP - because shooting twice is just silly" - JSOP, 2010 - You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 - When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
I'm not entirely sure what the ObjectTypeName, ObjectId and Topic members of NotificationViewModel point at. When I tested them for a notification for a comment to an answer, I got "Article" for ObjectTypeName, the answer ID for ObjectId and "Comment" for Topic. But when testing the same for a message on an article forum, I got "Forum Message" for ObjectTypeName, the message ID for ObjectId and "Forum Message" for Topic. This looked a bit odd to me because it was entirely different for the comment to the answer.
How do these properties actually work?
The quick brown ProgramFOX jumps right over the Lazy<Dog>.
Sorry, we have an error in our new and improved deployment script that is resulting in the incorrect configuration file being deploy. I'm doing a deploy the tried and true way and the site should be up in a few minutes.