@maxim_mazurok/gapi.client.calendar-v3 0.1.20251027 → 0.1.20251028

package/index.d.ts

@@ -9,7 +9,7 @@
 // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
 // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
 // Generated from: https://calendar-json.googleapis.com/$discovery/rest?version=v3
-// Revision: 20251027
+// Revision: 20251028
 
 /// <reference types="gapi.client" />
 
@@ -49,7 +49,8 @@ declare namespace gapi.client {
        * - "freeBusyReader" - Provides read access to free/busy information.
        * - "reader" - Provides read access to the calendar. Private events will appear to users with reader access, but event details will be hidden.
        * - "writer" - Provides read and write access to the calendar. Private events will appear to users with writer access, and event details will be visible. Provides read access to the calendar's ACLs.
-       * - "owner" - Provides ownership of the calendar. This role has all of the permissions of the writer role with the additional ability to manipulate ACLs.
+       * - "owner" - Provides manager access to the calendar. This role has all of the permissions of the writer role with the additional ability to modify access levels of other users.
+       * Important: the owner role is different from the calendar's data owner. A calendar has a single data owner, but can have multiple users with owner role.
        */
       role?: string;
       /** The extent to which calendar access is granted by this ACL rule. */
@@ -69,6 +70,8 @@ declare namespace gapi.client {
     interface Calendar {
       /** Conferencing properties for this calendar, for example what types of conferences are allowed. */
       conferenceProperties?: ConferenceProperties;
+      /** The email of the owner of the calendar. Set only for secondary calendars. Read-only. */
+      dataOwner?: string;
       /** Description of the calendar. Optional. */
       description?: string;
       /** ETag of the resource. */
@@ -102,7 +105,8 @@ declare namespace gapi.client {
        * - "freeBusyReader" - Provides read access to free/busy information.
        * - "reader" - Provides read access to the calendar. Private events will appear to users with reader access, but event details will be hidden.
        * - "writer" - Provides read and write access to the calendar. Private events will appear to users with writer access, and event details will be visible.
-       * - "owner" - Provides ownership of the calendar. This role has all of the permissions of the writer role with the additional ability to see and manipulate ACLs.
+       * - "owner" - Provides manager access to the calendar. This role has all of the permissions of the writer role with the additional ability to see and modify access levels of other users.
+       * Important: the owner role is different from the calendar's data owner. A calendar has a single data owner, but can have multiple users with owner role.
        */
       accessRole?: string;
       /** The main color of the calendar in the hexadecimal format "#0088aa". This property supersedes the index-based colorId property. To set or change this property, you need to specify colorRgbFormat=true in the parameters of the insert, update and patch methods. Optional. */
@@ -111,6 +115,8 @@ declare namespace gapi.client {
       colorId?: string;
       /** Conferencing properties for this calendar, for example what types of conferences are allowed. */
       conferenceProperties?: ConferenceProperties;
+      /** The email of the owner of the calendar. Set only for secondary calendars. Read-only. */
+      dataOwner?: string;
       /** The default reminders that the authenticated user has for this calendar. */
       defaultReminders?: EventReminder[];
       /** Whether this calendar list entry has been deleted from the calendar list. Read-only. Optional. The default is False. */
@@ -670,7 +676,8 @@ declare namespace gapi.client {
        * - "freeBusyReader" - The user has read access to free/busy information.
        * - "reader" - The user has read access to the calendar. Private events will appear to users with reader access, but event details will be hidden.
        * - "writer" - The user has read and write access to the calendar. Private events will appear to users with writer access, and event details will be visible.
-       * - "owner" - The user has ownership of the calendar. This role has all of the permissions of the writer role with the additional ability to see and manipulate ACLs.
+       * - "owner" - The user has manager access to the calendar. This role has all of the permissions of the writer role with the additional ability to see and modify access levels of other users.
+       * Important: the owner role is different from the calendar's data owner. A calendar has a single data owner, but can have multiple users with owner role.
        */
       accessRole?: string;
       /** The default reminders on the calendar for the authenticated user. These reminders apply to all events on this calendar that do not explicitly override them (i.e. do not have reminders.useDefault set to True). */
@@ -1425,7 +1432,12 @@ declare namespace gapi.client {
         /** Deprecated. Please use quotaUser instead. */
         userIp?: string;
       }): Request<Calendar>;
-      /** Creates a secondary calendar. */
+      /**
+       * Creates a secondary calendar.
+       * The authenticated user for the request is made the data owner of the new calendar.
+       *
+       * Note: We recommend to authenticate as the intended data owner of the calendar. You can use domain-wide delegation of authority to allow applications to act on behalf of a specific user. Don't use a service account for authentication. If you use a service account for authentication, the service account is the data owner, which can lead to unexpected behavior. For example, if a service account is the data owner, data ownership cannot be transferred.
+       */
       insert(request: {
         /** Data format for the response. */
         alt?: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maxim_mazurok/gapi.client.calendar-v3",
-  "version": "0.1.20251027",
+  "version": "0.1.20251028",
   "description": "TypeScript typings for Calendar API v3",
   "repository": {
     "type": "git",

package/readme.md

@@ -216,6 +216,9 @@ await gapi.client.calendar.calendars.get({calendarId: 'calendarId'});
 
 /*
 Creates a secondary calendar.
+The authenticated user for the request is made the data owner of the new calendar.
+
+Note: We recommend to authenticate as the intended data owner of the calendar. You can use domain-wide delegation of authority to allow applications to act on behalf of a specific user. Don't use a service account for authentication. If you use a service account for authentication, the service account is the data owner, which can lead to unexpected behavior. For example, if a service account is the data owner, data ownership cannot be transferred.
 */
 await gapi.client.calendar.calendars.insert({});