All GetXXXResponseContent types declare all fields as Optional in Management API

まず、Management API の .get() エンドポイントで使用される GetXXXResponseContent モデルを見つけ、フィールドをリンク先の API ドキュメントと比較します。常に存在するとドキュメントに記載されているフィールドを特定し、それらのレスポンスの型付けを非オプショナルに変更して、代表的なエンドポイント全体で更新されたアノテーションを確認します。

Checklist

• I have looked into the Readme and have not found a suitable solution or answer.
• I have looked into the API documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

The return types for .get() functions declare all fields to be optional. An example here for an organization:

class GetOrganizationResponseContent(UniversalBaseModel):
    id: typing.Optional[str] = pydantic.Field(default=None)
    """
    Organization identifier.
    """

    name: typing.Optional[str] = pydantic.Field(default=None)
    """
    The name of this organization.
    """

    display_name: typing.Optional[str] = pydantic.Field(default=None)
    """
    Friendly name of this organization.
    """

    branding: typing.Optional[OrganizationBranding] = None
    metadata: typing.Optional[OrganizationMetadata] = None
    token_quota: typing.Optional[TokenQuota] = None

However the API documentation does not say id, display_name or name can be None : https://auth0.com/docs/fr-ca/api/management/v2/organizations/get-organizations

This forces developers to correct the typing after the fact with typing.cast or disable typing of the concerned lines.

Reproduction

1. Call any endpoint in the Management API
2. Use a field that should never been None (for exemple user.email or user.id)
3. The IDE or type checker will warn you this field could be None.

Additional context

No response

auth0-python version

5.1.0

Python version

3.12