Is your feature request related to a problem? Please describe.
A feature I've overlooked is that APODs are available in multiple languages.
Describe the feature you'd like
The API does not support it, so sadly I can't return localized descriptions or titles without web scraping (which is outside of the scope for an API wrapper). I can however support different languages with the GetPermalink method and then give them a link to the localized website instead.
Since the only way I see myself using localization at this point would be with the GetPermalink method, I don't think it's worth setting up a new field for the client that keeps track of the current localization. It should default to english and do error checking if it's something else to make sure that it's a valid language. If there's no good language entity in c# I'll just create my own, that way I won't have to do any error checking either.
There should maybe be some warnings that the links aren't guaranteed to work. Actually, maybe I could check if the link returns a valid HTTP status code and if not, give them the english one by default. That makes more sense to me, and gives a better user experience.
Is your feature request related to a problem? Please describe. A feature I've overlooked is that APODs are available in multiple languages.
Describe the feature you'd like The API does not support it, so sadly I can't return localized descriptions or titles without web scraping (which is outside of the scope for an API wrapper). I can however support different languages with the GetPermalink method and then give them a link to the localized website instead.
Since the only way I see myself using localization at this point would be with the GetPermalink method, I don't think it's worth setting up a new field for the client that keeps track of the current localization. It should default to english and do error checking if it's something else to make sure that it's a valid language. If there's no good language entity in c# I'll just create my own, that way I won't have to do any error checking either.
There should maybe be some warnings that the links aren't guaranteed to work. Actually, maybe I could check if the link returns a valid HTTP status code and if not, give them the english one by default. That makes more sense to me, and gives a better user experience.
Additional context
