Remove datatype inconsistencies in API responses
Here and there it happens that the datatypes of the returned JSON response is inconsistent.
When querying the user settings through account/settings the age of the user is an empty string in opposite to an int value if not set by the user.
"fullname" becomes null instead of string.
When querying data with ratings in it, the simple rating attribute consists of either "love" or "hate" (strings), but if the user has not rated that particular movie/show that value is false (boolean).
While null instead of an emtpy string is debatable since JSON and many if not all implementations of it fully support null values, programming languages with datatypes are getting veery angry when they expect a string but get a boolean, or int and get string.
Please fix this unexpected behaviour. Either use a null value for unknown values for everything or default values of the same datatype but not different datatypes here, null there and default values there.
It's a nightmare for a developer of 3rd party apps/plugins.
Trakt 2.0 API is much more consistent.
That is reassuring but I hope you find all inconsistencies that are present for now.
Like, the tvdb_ids in recommendation API functions are strings but for show/movie functions and most (I don't dare to say all) other API functions integer.
Is there any timeline/time you plan on releasing v2?