Skip to content

Outdated or missing typings for some Google APIs in TypeScript #3722

@ritikkumar8z

Description

@ritikkumar8z

I noticed that some Google APIs included in this client library have incomplete or outdated TypeScript typings, which makes it harder to use them with strict type checking. For example, certain newer API endpoints or parameters don’t appear in the generated typings, causing TypeScript errors or the need for manual overrides.

Steps to reproduce

Use the client with TypeScript.

Import and try to call methods from a recently added or less common API.

TypeScript shows missing types or incorrect signatures.

Expected behavior

Up-to-date and complete typings that cover all available APIs and their latest features.

No need for manual @ts-ignore or custom type declarations.

Additional context
This would greatly improve developer experience and reduce bugs when using the client in TypeScript projects.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs more infoThis issue needs more information from the customer to proceed.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions