[FEATURE] The issue of attribute names for objects

[zhenghaoyang24]

Is your feature request related to a problem? Please describe.

1. For return data of some interfaces, the same object field is missing, resulting in inconsistent types in TS development for example.

Here is an example:
In the api for obtaining driver ranking ( /2025/drivers-championship ), there is a driver object in the acquired array. There is no driverId in it and it is extracted externally. In the interface for obtaining team ranking (/2025/constructors-championship) , team object does not have teamId. I suggest that no matter which interface, the same object should maintain its integrity ( such as ), otherwise type determination will be difficult.

Api api/[year]/constructors-championship have no teamId and firstAppeareance became firstAppareance:

Api api/[year]/drivers-championship have no driverId:

Api api/[year]/teams have no birthday and national became teamNationality

2. Each api returns an array of objects with different property name:

In Api api/drivers ,it is drivers :

In Api api/seasons, it is championships :

in Api api/[year]/[round] ,it is races:

........

This may seen like a small problem, but if i want to get this array object, it means I have to use a different property name. I recommend using the uniform attribute name: data.