Repository navigation
Enhance types generation #3542
Description
Is your feature request related to a problem? Please describe.
Currently, all types are optional, or at least a lot of them. See: https://github.com/search?q=repo:googleapis/google-api-nodejs-client+%22%7C+null%22&type=code So, this leads to an awful development experience.
For example, see Google Calendar API:
But on the other hand, we can see in docs that some fields are optional and some are not.
https://developers.google.com/calendar/api/v3/reference/events#resource
Describe the solution you'd like
I would like to see real types with the minimum amount of optional fields.
Describe alternatives you've considered
Of course, we can check everything manually or disable TypeScript checking at all. But I believe it's not a good solution, as why do we need typings which do not work.
#3151
Activity
Yuripetusko commentedon Jan 30, 2026
This makes it even harder to implement I am guessing due to FieldMask standard query string where any caller can select which fields should be returned. So the library would have to infer types based on
fieldsstring that is passed as$fieldsquery param to API. The devloper experience is prettu bad I agree, but also I can imagine that this is a tough one, especially since most types are generated from json schema that is itself generated from protobuff definitions I believe