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
The API has some inconsistancies between the schemas. for example, TV and Movie both use the SpokenLanguages but both have different field names:
class SpokenLanguagesModelTv(BaseModel):
"""
Data class representing a spoken language.
"""
englishName: str
iso_639_1: str
name: str
class SpokenLanguagesModelMovie(BaseModel):
"""
Data class representing a spoken language.
"""
english_name: str
iso_639_1: str
name: str
Desired Behavior
standardise schemas where it makes sense, the english name should either be "englishName" or "english_name" allowing the same schema for both TV and Movie for easier use of the API
Additional Context
No response
Code of Conduct
I agree to follow Overseerr's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
The API has some inconsistancies between the schemas. for example, TV and Movie both use the SpokenLanguages but both have different field names:
Desired Behavior
standardise schemas where it makes sense, the english name should either be "englishName" or "english_name" allowing the same schema for both TV and Movie for easier use of the API
Additional Context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: