google-apis-chat_v1 0.68.0 → 0.69.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (6) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +4 -0
  3. data/lib/google/apis/chat_v1/classes.rb +126 -127
  4. data/lib/google/apis/chat_v1/gem_version.rb +2 -2
  5. data/lib/google/apis/chat_v1/service.rb +42 -66
  6. metadata +4 -4
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 5612946e363951d77cf43c85a687c12b56869136c97a6298a704e866acb251cc
4
- data.tar.gz: 2888c3afc13c516435eb4d3f5551463b910a85d93aa967e9d118b854ab16cd93
3
+ metadata.gz: df4c97a8aa2870c8769d840ac03e39a3269f8def78f6539363951f5bb6c1512c
4
+ data.tar.gz: d4f7361c06aadb5065c931203c3bbffa87fb2fb4ae1ba0a5a548b1317047cf7a
5
5
  SHA512:
6
- metadata.gz: 04d84e3f5dde32844dd849f33a8c5c94ff9626dfccdbd157cfac4c54eb9cd717e928eb3e0a1b4153fb3e75393e9318accc682eb2137be1fb1d86508fd4ca1286
7
- data.tar.gz: 453ece9fe07a69b08380809694e86879c233fe2391152eea3c06b67fc5748ee0dba0b987b2a87bb919b4b999dc2cf7de3299832ed507f7eb9724d46f952db368
6
+ metadata.gz: 386187890b91c6a6dec65fd3062682616a353d3caab5138ab5d2585ef3ecb22f2e0218a7d3c40b55b98bce39d5aa46fadf8e2a55909609691156b6417a9f35b2
7
+ data.tar.gz: 2e200fad6dd01013bf107a1343e17f51c57d296172baa606304d84349cd6ed18fecf7e55c4034ce94563cbfd80b056cc781514c62273f66aa8b622f14a4e455b
data/CHANGELOG.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # Release history for google-apis-chat_v1
2
2
 
3
+ ### v0.69.0 (2023-08-27)
4
+
5
+ * Regenerated from discovery document revision 20230822
6
+
3
7
  ### v0.68.0 (2023-08-13)
4
8
 
5
9
  * Regenerated from discovery document revision 20230806
data/lib/google/apis/chat_v1/classes.rb CHANGED
@@ -402,41 +402,42 @@ module Google
402
402
  end
403
403
  end
404
404
 
405
- # Widgets for Chat apps to specify.
405
+ # A [card](https://developers.google.com/chat/api/reference/rest/v1/cards) in a
406
+ # Google Chat message. Only Chat apps can create cards. If your Chat app [
407
+ # authenticates as a user](https://developers.google.com/chat/api/guides/auth/
408
+ # users), the message can't contain cards.
406
409
  class CardWithId
407
410
  include Google::Apis::Core::Hashable
408
411
 
409
- # Cards support a defined layout, interactive UI elements like buttons, and rich
410
- # media like images. Use cards to present detailed information, gather
411
- # information from users, and guide users to take a next step. In Google Chat,
412
- # cards appear in several places: - As stand-alone messages. - Accompanying a
413
- # text message, just beneath the text message. - As a [dialog](https://
414
- # developers.google.com/chat/how-tos/dialogs). The following example JSON
415
- # creates a "contact card" that features: - A header with the contact's name,
416
- # job title, and avatar picture. - A section with the contact information,
417
- # including formatted text. - Buttons that users can click to share the contact,
418
- # or see more or less information. For more examples, see [Design dynamic,
419
- # interactive, and consistent UIs with cards](https://developers.google.com/chat/
420
- # ui). ![Example contact card](https://developers.google.com/chat/images/
421
- # card_api_reference.png) ``` ` "cardsV2": [ ` "cardId": "unique-card-id", "card"
422
- # : ` "header": ` "title": "Sasha", "subtitle": "Software Engineer", "imageUrl":
423
- # "https://developers.google.com/chat/images/quickstart-app-avatar.png", "
424
- # imageType": "CIRCLE", "imageAltText": "Avatar for Sasha", `, "sections": [ ` "
425
- # header": "Contact Info", "collapsible": true, "uncollapsibleWidgetsCount": 1, "
426
- # widgets": [ ` "decoratedText": ` "startIcon": ` "knownIcon": "EMAIL", `, "text"
427
- # : "sasha@example.com", ` `, ` "decoratedText": ` "startIcon": ` "knownIcon": "
428
- # PERSON", `, "text": "Online", `, `, ` "decoratedText": ` "startIcon": ` "
429
- # knownIcon": "PHONE", `, "text": "+1 (555) 555-1234", ` `, ` "buttonList": ` "
430
- # buttons": [ ` "text": "Share", "onClick": ` "openLink": ` "url": "https://
431
- # example.com/share", ` ` `, ` "text": "Edit", "onClick": ` "action": ` "
432
- # function": "goToView", "parameters": [ ` "key": "viewType", "value": "EDIT", `
433
- # ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
412
+ # A card interface displayed in a Google Chat message or Google Workspace Add-on.
413
+ # Cards support a defined layout, interactive UI elements like buttons, and
414
+ # rich media like images. Use cards to present detailed information, gather
415
+ # information from users, and guide users to take a next step. To learn how to
416
+ # build cards, see the following documentation: * For Google Chat apps, see [
417
+ # Design dynamic, interactive, and consistent UIs with cards](https://developers.
418
+ # google.com/chat/ui). * For Google Workspace Add-ons, see [Card-based
419
+ # interfaces](https://developers.google.com/apps-script/add-ons/concepts/cards).
420
+ # **Example: Card message for a Google Chat app** ![Example contact card](https:/
421
+ # /developers.google.com/chat/images/card_api_reference.png) To create the
422
+ # sample card message in Google Chat, use the following JSON: ``` ` "cardsV2": [
423
+ # ` "cardId": "unique-card-id", "card": ` "header": ` "title": "Sasha", "
424
+ # subtitle": "Software Engineer", "imageUrl": "https://developers.google.com/
425
+ # chat/images/quickstart-app-avatar.png", "imageType": "CIRCLE", "imageAltText":
426
+ # "Avatar for Sasha", `, "sections": [ ` "header": "Contact Info", "collapsible":
427
+ # true, "uncollapsibleWidgetsCount": 1, "widgets": [ ` "decoratedText": ` "
428
+ # startIcon": ` "knownIcon": "EMAIL", `, "text": "sasha@example.com", ` `, ` "
429
+ # decoratedText": ` "startIcon": ` "knownIcon": "PERSON", `, "text": "Online", `,
430
+ # `, ` "decoratedText": ` "startIcon": ` "knownIcon": "PHONE", `, "text": "+1 (
431
+ # 555) 555-1234", ` `, ` "buttonList": ` "buttons": [ ` "text": "Share", "
432
+ # onClick": ` "openLink": ` "url": "https://example.com/share", ` ` `, ` "text":
433
+ # "Edit", "onClick": ` "action": ` "function": "goToView", "parameters": [ ` "
434
+ # key": "viewType", "value": "EDIT", ` ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
434
435
  # Corresponds to the JSON property `card`
435
436
  # @return [Google::Apis::ChatV1::GoogleAppsCardV1Card]
436
437
  attr_accessor :card
437
438
 
438
- # Required for `cardsV2` messages. Chat app-specified identifier for this widget.
439
- # Scoped within a message.
439
+ # Required if the message contains multiple cards. A unique identifier for a
440
+ # card in a message.
440
441
  # Corresponds to the JSON property `cardId`
441
442
  # @return [String]
442
443
  attr_accessor :card_id
@@ -768,9 +769,12 @@ module Google
768
769
  end
769
770
  end
770
771
 
771
- # Google Chat events. To learn how to use events, see [Receive and respond to
772
- # Google Chat events](https://developers.google.com/chat/api/guides/message-
773
- # formats).
772
+ # A Google Chat app interaction event. To learn about interaction events, see [
773
+ # Receive and respond to interactions with your Google Chat app](https://
774
+ # developers.google.com/chat/api/guides/message-formats). To learn about event
775
+ # types and for example event payloads, see [Types of Google Chat app
776
+ # interaction events](https://developers.google.com/chat/api/guides/message-
777
+ # formats/events).
774
778
  class DeprecatedEvent
775
779
  include Google::Apis::Core::Hashable
776
780
 
@@ -796,25 +800,25 @@ module Google
796
800
  # @return [String]
797
801
  attr_accessor :config_complete_redirect_url
798
802
 
799
- # The type of [dialog](https://developers.google.com/chat/how-tos/dialogs) event
800
- # received.
803
+ # The type of [dialog](https://developers.google.com/chat/how-tos/dialogs)
804
+ # interaction event received.
801
805
  # Corresponds to the JSON property `dialogEventType`
802
806
  # @return [String]
803
807
  attr_accessor :dialog_event_type
804
808
 
805
- # The timestamp indicating when the event occurred.
809
+ # The timestamp indicating when the interaction event occurred.
806
810
  # Corresponds to the JSON property `eventTime`
807
811
  # @return [String]
808
812
  attr_accessor :event_time
809
813
 
810
- # True when the event is related to [dialogs](https://developers.google.com/chat/
811
- # how-tos/dialogs).
814
+ # For `CARD_CLICKED` interaction events, whether the user interacted with a [
815
+ # dialog](https://developers.google.com/chat/how-tos/dialogs).
812
816
  # Corresponds to the JSON property `isDialogEvent`
813
817
  # @return [Boolean]
814
818
  attr_accessor :is_dialog_event
815
819
  alias_method :is_dialog_event?, :is_dialog_event
816
820
 
817
- # A message in Google Chat.
821
+ # A message in a Google Chat space.
818
822
  # Corresponds to the JSON property `message`
819
823
  # @return [Google::Apis::ChatV1::Message]
820
824
  attr_accessor :message
@@ -825,9 +829,9 @@ module Google
825
829
  # @return [Google::Apis::ChatV1::Space]
826
830
  attr_accessor :space
827
831
 
828
- # The Chat app-defined key for the thread related to the event. See [`spaces.
829
- # messages.thread.threadKey`](/chat/api/reference/rest/v1/spaces.messages#Thread.
830
- # FIELDS.thread_key) for more information.
832
+ # The Chat app-defined key for the thread related to the interaction event. See [
833
+ # `spaces.messages.thread.threadKey`](/chat/api/reference/rest/v1/spaces.
834
+ # messages#Thread.FIELDS.thread_key) for more information.
831
835
  # Corresponds to the JSON property `threadKey`
832
836
  # @return [String]
833
837
  attr_accessor :thread_key
@@ -843,7 +847,9 @@ module Google
843
847
  # @return [String]
844
848
  attr_accessor :token
845
849
 
846
- # The type of the event.
850
+ # The type of interaction event. For details, see [Types of Google Chat app
851
+ # interaction events](https://developers.google.com/chat/api/guides/message-
852
+ # formats/events).
847
853
  # Corresponds to the JSON property `type`
848
854
  # @return [String]
849
855
  attr_accessor :type
@@ -881,31 +887,29 @@ module Google
881
887
  class Dialog
882
888
  include Google::Apis::Core::Hashable
883
889
 
884
- # Cards support a defined layout, interactive UI elements like buttons, and rich
885
- # media like images. Use cards to present detailed information, gather
886
- # information from users, and guide users to take a next step. In Google Chat,
887
- # cards appear in several places: - As stand-alone messages. - Accompanying a
888
- # text message, just beneath the text message. - As a [dialog](https://
889
- # developers.google.com/chat/how-tos/dialogs). The following example JSON
890
- # creates a "contact card" that features: - A header with the contact's name,
891
- # job title, and avatar picture. - A section with the contact information,
892
- # including formatted text. - Buttons that users can click to share the contact,
893
- # or see more or less information. For more examples, see [Design dynamic,
894
- # interactive, and consistent UIs with cards](https://developers.google.com/chat/
895
- # ui). ![Example contact card](https://developers.google.com/chat/images/
896
- # card_api_reference.png) ``` ` "cardsV2": [ ` "cardId": "unique-card-id", "card"
897
- # : ` "header": ` "title": "Sasha", "subtitle": "Software Engineer", "imageUrl":
898
- # "https://developers.google.com/chat/images/quickstart-app-avatar.png", "
899
- # imageType": "CIRCLE", "imageAltText": "Avatar for Sasha", `, "sections": [ ` "
900
- # header": "Contact Info", "collapsible": true, "uncollapsibleWidgetsCount": 1, "
901
- # widgets": [ ` "decoratedText": ` "startIcon": ` "knownIcon": "EMAIL", `, "text"
902
- # : "sasha@example.com", ` `, ` "decoratedText": ` "startIcon": ` "knownIcon": "
903
- # PERSON", `, "text": "Online", `, `, ` "decoratedText": ` "startIcon": ` "
904
- # knownIcon": "PHONE", `, "text": "+1 (555) 555-1234", ` `, ` "buttonList": ` "
905
- # buttons": [ ` "text": "Share", "onClick": ` "openLink": ` "url": "https://
906
- # example.com/share", ` ` `, ` "text": "Edit", "onClick": ` "action": ` "
907
- # function": "goToView", "parameters": [ ` "key": "viewType", "value": "EDIT", `
908
- # ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
890
+ # A card interface displayed in a Google Chat message or Google Workspace Add-on.
891
+ # Cards support a defined layout, interactive UI elements like buttons, and
892
+ # rich media like images. Use cards to present detailed information, gather
893
+ # information from users, and guide users to take a next step. To learn how to
894
+ # build cards, see the following documentation: * For Google Chat apps, see [
895
+ # Design dynamic, interactive, and consistent UIs with cards](https://developers.
896
+ # google.com/chat/ui). * For Google Workspace Add-ons, see [Card-based
897
+ # interfaces](https://developers.google.com/apps-script/add-ons/concepts/cards).
898
+ # **Example: Card message for a Google Chat app** ![Example contact card](https:/
899
+ # /developers.google.com/chat/images/card_api_reference.png) To create the
900
+ # sample card message in Google Chat, use the following JSON: ``` ` "cardsV2": [
901
+ # ` "cardId": "unique-card-id", "card": ` "header": ` "title": "Sasha", "
902
+ # subtitle": "Software Engineer", "imageUrl": "https://developers.google.com/
903
+ # chat/images/quickstart-app-avatar.png", "imageType": "CIRCLE", "imageAltText":
904
+ # "Avatar for Sasha", `, "sections": [ ` "header": "Contact Info", "collapsible":
905
+ # true, "uncollapsibleWidgetsCount": 1, "widgets": [ ` "decoratedText": ` "
906
+ # startIcon": ` "knownIcon": "EMAIL", `, "text": "sasha@example.com", ` `, ` "
907
+ # decoratedText": ` "startIcon": ` "knownIcon": "PERSON", `, "text": "Online", `,
908
+ # `, ` "decoratedText": ` "startIcon": ` "knownIcon": "PHONE", `, "text": "+1 (
909
+ # 555) 555-1234", ` `, ` "buttonList": ` "buttons": [ ` "text": "Share", "
910
+ # onClick": ` "openLink": ` "url": "https://example.com/share", ` ` `, ` "text":
911
+ # "Edit", "onClick": ` "action": ` "function": "goToView", "parameters": [ ` "
912
+ # key": "viewType", "value": "EDIT", ` ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
909
913
  # Corresponds to the JSON property `body`
910
914
  # @return [Google::Apis::ChatV1::GoogleAppsCardV1Card]
911
915
  attr_accessor :body
@@ -1364,31 +1368,29 @@ module Google
1364
1368
  end
1365
1369
  end
1366
1370
 
1367
- # Cards support a defined layout, interactive UI elements like buttons, and rich
1368
- # media like images. Use cards to present detailed information, gather
1369
- # information from users, and guide users to take a next step. In Google Chat,
1370
- # cards appear in several places: - As stand-alone messages. - Accompanying a
1371
- # text message, just beneath the text message. - As a [dialog](https://
1372
- # developers.google.com/chat/how-tos/dialogs). The following example JSON
1373
- # creates a "contact card" that features: - A header with the contact's name,
1374
- # job title, and avatar picture. - A section with the contact information,
1375
- # including formatted text. - Buttons that users can click to share the contact,
1376
- # or see more or less information. For more examples, see [Design dynamic,
1377
- # interactive, and consistent UIs with cards](https://developers.google.com/chat/
1378
- # ui). ![Example contact card](https://developers.google.com/chat/images/
1379
- # card_api_reference.png) ``` ` "cardsV2": [ ` "cardId": "unique-card-id", "card"
1380
- # : ` "header": ` "title": "Sasha", "subtitle": "Software Engineer", "imageUrl":
1381
- # "https://developers.google.com/chat/images/quickstart-app-avatar.png", "
1382
- # imageType": "CIRCLE", "imageAltText": "Avatar for Sasha", `, "sections": [ ` "
1383
- # header": "Contact Info", "collapsible": true, "uncollapsibleWidgetsCount": 1, "
1384
- # widgets": [ ` "decoratedText": ` "startIcon": ` "knownIcon": "EMAIL", `, "text"
1385
- # : "sasha@example.com", ` `, ` "decoratedText": ` "startIcon": ` "knownIcon": "
1386
- # PERSON", `, "text": "Online", `, `, ` "decoratedText": ` "startIcon": ` "
1387
- # knownIcon": "PHONE", `, "text": "+1 (555) 555-1234", ` `, ` "buttonList": ` "
1388
- # buttons": [ ` "text": "Share", "onClick": ` "openLink": ` "url": "https://
1389
- # example.com/share", ` ` `, ` "text": "Edit", "onClick": ` "action": ` "
1390
- # function": "goToView", "parameters": [ ` "key": "viewType", "value": "EDIT", `
1391
- # ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
1371
+ # A card interface displayed in a Google Chat message or Google Workspace Add-on.
1372
+ # Cards support a defined layout, interactive UI elements like buttons, and
1373
+ # rich media like images. Use cards to present detailed information, gather
1374
+ # information from users, and guide users to take a next step. To learn how to
1375
+ # build cards, see the following documentation: * For Google Chat apps, see [
1376
+ # Design dynamic, interactive, and consistent UIs with cards](https://developers.
1377
+ # google.com/chat/ui). * For Google Workspace Add-ons, see [Card-based
1378
+ # interfaces](https://developers.google.com/apps-script/add-ons/concepts/cards).
1379
+ # **Example: Card message for a Google Chat app** ![Example contact card](https:/
1380
+ # /developers.google.com/chat/images/card_api_reference.png) To create the
1381
+ # sample card message in Google Chat, use the following JSON: ``` ` "cardsV2": [
1382
+ # ` "cardId": "unique-card-id", "card": ` "header": ` "title": "Sasha", "
1383
+ # subtitle": "Software Engineer", "imageUrl": "https://developers.google.com/
1384
+ # chat/images/quickstart-app-avatar.png", "imageType": "CIRCLE", "imageAltText":
1385
+ # "Avatar for Sasha", `, "sections": [ ` "header": "Contact Info", "collapsible":
1386
+ # true, "uncollapsibleWidgetsCount": 1, "widgets": [ ` "decoratedText": ` "
1387
+ # startIcon": ` "knownIcon": "EMAIL", `, "text": "sasha@example.com", ` `, ` "
1388
+ # decoratedText": ` "startIcon": ` "knownIcon": "PERSON", `, "text": "Online", `,
1389
+ # `, ` "decoratedText": ` "startIcon": ` "knownIcon": "PHONE", `, "text": "+1 (
1390
+ # 555) 555-1234", ` `, ` "buttonList": ` "buttons": [ ` "text": "Share", "
1391
+ # onClick": ` "openLink": ` "url": "https://example.com/share", ` ` `, ` "text":
1392
+ # "Edit", "onClick": ` "action": ` "function": "goToView", "parameters": [ ` "
1393
+ # key": "viewType", "value": "EDIT", ` ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
1392
1394
  class GoogleAppsCardV1Card
1393
1395
  include Google::Apis::Core::Hashable
1394
1396
 
@@ -2112,31 +2114,29 @@ module Google
2112
2114
  # @return [Google::Apis::ChatV1::GoogleAppsCardV1Action]
2113
2115
  attr_accessor :action
2114
2116
 
2115
- # Cards support a defined layout, interactive UI elements like buttons, and rich
2116
- # media like images. Use cards to present detailed information, gather
2117
- # information from users, and guide users to take a next step. In Google Chat,
2118
- # cards appear in several places: - As stand-alone messages. - Accompanying a
2119
- # text message, just beneath the text message. - As a [dialog](https://
2120
- # developers.google.com/chat/how-tos/dialogs). The following example JSON
2121
- # creates a "contact card" that features: - A header with the contact's name,
2122
- # job title, and avatar picture. - A section with the contact information,
2123
- # including formatted text. - Buttons that users can click to share the contact,
2124
- # or see more or less information. For more examples, see [Design dynamic,
2125
- # interactive, and consistent UIs with cards](https://developers.google.com/chat/
2126
- # ui). ![Example contact card](https://developers.google.com/chat/images/
2127
- # card_api_reference.png) ``` ` "cardsV2": [ ` "cardId": "unique-card-id", "card"
2128
- # : ` "header": ` "title": "Sasha", "subtitle": "Software Engineer", "imageUrl":
2129
- # "https://developers.google.com/chat/images/quickstart-app-avatar.png", "
2130
- # imageType": "CIRCLE", "imageAltText": "Avatar for Sasha", `, "sections": [ ` "
2131
- # header": "Contact Info", "collapsible": true, "uncollapsibleWidgetsCount": 1, "
2132
- # widgets": [ ` "decoratedText": ` "startIcon": ` "knownIcon": "EMAIL", `, "text"
2133
- # : "sasha@example.com", ` `, ` "decoratedText": ` "startIcon": ` "knownIcon": "
2134
- # PERSON", `, "text": "Online", `, `, ` "decoratedText": ` "startIcon": ` "
2135
- # knownIcon": "PHONE", `, "text": "+1 (555) 555-1234", ` `, ` "buttonList": ` "
2136
- # buttons": [ ` "text": "Share", "onClick": ` "openLink": ` "url": "https://
2137
- # example.com/share", ` ` `, ` "text": "Edit", "onClick": ` "action": ` "
2138
- # function": "goToView", "parameters": [ ` "key": "viewType", "value": "EDIT", `
2139
- # ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
2117
+ # A card interface displayed in a Google Chat message or Google Workspace Add-on.
2118
+ # Cards support a defined layout, interactive UI elements like buttons, and
2119
+ # rich media like images. Use cards to present detailed information, gather
2120
+ # information from users, and guide users to take a next step. To learn how to
2121
+ # build cards, see the following documentation: * For Google Chat apps, see [
2122
+ # Design dynamic, interactive, and consistent UIs with cards](https://developers.
2123
+ # google.com/chat/ui). * For Google Workspace Add-ons, see [Card-based
2124
+ # interfaces](https://developers.google.com/apps-script/add-ons/concepts/cards).
2125
+ # **Example: Card message for a Google Chat app** ![Example contact card](https:/
2126
+ # /developers.google.com/chat/images/card_api_reference.png) To create the
2127
+ # sample card message in Google Chat, use the following JSON: ``` ` "cardsV2": [
2128
+ # ` "cardId": "unique-card-id", "card": ` "header": ` "title": "Sasha", "
2129
+ # subtitle": "Software Engineer", "imageUrl": "https://developers.google.com/
2130
+ # chat/images/quickstart-app-avatar.png", "imageType": "CIRCLE", "imageAltText":
2131
+ # "Avatar for Sasha", `, "sections": [ ` "header": "Contact Info", "collapsible":
2132
+ # true, "uncollapsibleWidgetsCount": 1, "widgets": [ ` "decoratedText": ` "
2133
+ # startIcon": ` "knownIcon": "EMAIL", `, "text": "sasha@example.com", ` `, ` "
2134
+ # decoratedText": ` "startIcon": ` "knownIcon": "PERSON", `, "text": "Online", `,
2135
+ # `, ` "decoratedText": ` "startIcon": ` "knownIcon": "PHONE", `, "text": "+1 (
2136
+ # 555) 555-1234", ` `, ` "buttonList": ` "buttons": [ ` "text": "Share", "
2137
+ # onClick": ` "openLink": ` "url": "https://example.com/share", ` ` `, ` "text":
2138
+ # "Edit", "onClick": ` "action": ` "function": "goToView", "parameters": [ ` "
2139
+ # key": "viewType", "value": "EDIT", ` ], ` ` `, ], ` `, ], `, ], `, ` ], ` ```
2140
2140
  # Corresponds to the JSON property `card`
2141
2141
  # @return [Google::Apis::ChatV1::GoogleAppsCardV1Card]
2142
2142
  attr_accessor :card
@@ -2971,7 +2971,9 @@ module Google
2971
2971
  end
2972
2972
  end
2973
2973
 
2974
- # Types of data inputs for widgets. Users enter data with these inputs.
2974
+ # Types of data that users can enter on cards or dialogs. To learn how to
2975
+ # process information from users, see [Read form data input by users on cards](
2976
+ # https://developers.google.com/chat/ui/read-form-data).
2975
2977
  class Inputs
2976
2978
  include Google::Apis::Core::Hashable
2977
2979
 
@@ -3280,7 +3282,7 @@ module Google
3280
3282
  end
3281
3283
  end
3282
3284
 
3283
- # A message in Google Chat.
3285
+ # A message in a Google Chat space.
3284
3286
  class Message
3285
3287
  include Google::Apis::Core::Hashable
3286
3288
 
@@ -3318,15 +3320,12 @@ module Google
3318
3320
  # @return [Array<Google::Apis::ChatV1::Card>]
3319
3321
  attr_accessor :cards
3320
3322
 
3321
- # Richly formatted and interactive cards that display UI elements and editable
3322
- # widgets, such as: - Formatted text - Buttons - Clickable images - Checkboxes -
3323
- # Radio buttons - Input widgets. Cards are usually displayed below the text body
3324
- # of a Chat message, but can situationally appear other places, such as [dialogs]
3325
- # (https://developers.google.com/chat/how-tos/dialogs). Each card can have a
3326
- # maximum size of 32 KB. The `cardId` is a unique identifier among cards in the
3327
- # same message and for identifying user input values. Currently supported
3328
- # widgets include: - `TextParagraph` - `DecoratedText` - `Image` - `ButtonList` -
3329
- # `Divider` - `TextInput` - `SelectionInput` - `Grid`
3323
+ # An array of [cards](https://developers.google.com/chat/api/reference/rest/v1/
3324
+ # cards). Only Chat apps can create cards. If your Chat app [authenticates as a
3325
+ # user](https://developers.google.com/chat/api/guides/auth/users), the messages
3326
+ # can't contain cards. To learn about cards and how to create them, see [Design
3327
+ # dynamic, interactive, and consistent UIs with cards](https://developers.google.
3328
+ # com/chat/ui).
3330
3329
  # Corresponds to the JSON property `cardsV2`
3331
3330
  # @return [Array<Google::Apis::ChatV1::CardWithId>]
3332
3331
  attr_accessor :cards_v2
data/lib/google/apis/chat_v1/gem_version.rb CHANGED
@@ -16,13 +16,13 @@ module Google
16
16
  module Apis
17
17
  module ChatV1
18
18
  # Version of the google-apis-chat_v1 gem
19
- GEM_VERSION = "0.68.0"
19
+ GEM_VERSION = "0.69.0"
20
20
 
21
21
  # Version of the code generator used to generate this client
22
22
  GENERATOR_VERSION = "0.12.0"
23
23
 
24
24
  # Revision of the discovery document this client was generated from
25
- REVISION = "20230806"
25
+ REVISION = "20230822"
26
26
  end
27
27
  end
28
28
  end
data/lib/google/apis/chat_v1/service.rb CHANGED
@@ -91,9 +91,8 @@ module Google
91
91
  # Uploads an attachment. For an example, see [Upload media as a file attachment](
92
92
  # https://developers.google.com/chat/api/guides/v1/media-and-attachments/upload).
93
93
  # Requires user [authentication](https://developers.google.com/chat/api/guides/
94
- # auth/users) and the `chat.messages` or `chat.messages.create` authorization
95
- # scope. You can upload attachments up to 200 MB. Certain file types aren't
96
- # supported. For details, see [File types blocked by Google Chat](https://
94
+ # auth/users). You can upload attachments up to 200 MB. Certain file types aren'
95
+ # t supported. For details, see [File types blocked by Google Chat](https://
97
96
  # support.google.com/chat/answer/7651457?&co=GENIE.Platform%3DDesktop#File%
98
97
  # 20types%20blocked%20in%20Google%20Chat).
99
98
  # @param [String] parent
@@ -144,8 +143,7 @@ module Google
144
143
  # spaces/create). If you receive the error message `ALREADY_EXISTS` when
145
144
  # creating a space, try a different `displayName`. An existing space within the
146
145
  # Google Workspace organization might already use this display name. Requires [
147
- # user authentication](https://developers.google.com/chat/api/guides/auth/users)
148
- # and the `chat.spaces.create` or `chat.spaces` scope.
146
+ # user authentication](https://developers.google.com/chat/api/guides/auth/users).
149
147
  # @param [Google::Apis::ChatV1::Space] space_object
150
148
  # @param [String] request_id
151
149
  # Optional. A unique identifier for this request. A random UUID is recommended.
@@ -186,7 +184,7 @@ module Google
186
184
  # in the space—are also deleted. For an example, see [Delete a space](https://
187
185
  # developers.google.com/chat/api/guides/v1/spaces/delete). Requires [user
188
186
  # authentication](https://developers.google.com/chat/api/guides/auth/users) from
189
- # a user who has permission to delete the space, and the `chat.delete` scope.
187
+ # a user who has permission to delete the space.
190
188
  # @param [String] name
191
189
  # Required. Resource name of the space to delete. Format: `spaces/`space``
192
190
  # @param [String] fields
@@ -271,8 +269,7 @@ module Google
271
269
  # account authentication](https://developers.google.com/chat/api/guides/auth/
272
270
  # service-accounts) and [user authentication](https://developers.google.com/chat/
273
271
  # api/guides/auth/users). [User authentication](https://developers.google.com/
274
- # chat/api/guides/auth/users) requires the `chat.spaces` or `chat.spaces.
275
- # readonly` authorization scope.
272
+ # chat/api/guides/auth/users).
276
273
  # @param [String] name
277
274
  # Required. Resource name of the space, in the form "spaces/*". Format: `spaces/`
278
275
  # space``
@@ -309,8 +306,7 @@ module Google
309
306
  # authentication](https://developers.google.com/chat/api/guides/auth). Fully
310
307
  # supports [service account authentication](https://developers.google.com/chat/
311
308
  # api/guides/auth/service-accounts) and [user authentication](https://developers.
312
- # google.com/chat/api/guides/auth/users) requires the `chat.spaces` or `chat.
313
- # spaces.readonly` authorization scope. Lists spaces visible to the caller or
309
+ # google.com/chat/api/guides/auth/users). Lists spaces visible to the caller or
314
310
  # authenticated user. Group chats and DMs aren't listed until the first message
315
311
  # is sent.
316
312
  # @param [String] filter
@@ -371,8 +367,7 @@ module Google
371
367
  # displayName` field and receive the error message `ALREADY_EXISTS`, try a
372
368
  # different display name.. An existing space within the Google Workspace
373
369
  # organization might already use this display name. Requires [user
374
- # authentication](https://developers.google.com/chat/api/guides/auth/users) and
375
- # the `chat.spaces` scope.
370
+ # authentication](https://developers.google.com/chat/api/guides/auth/users).
376
371
  # @param [String] name
377
372
  # Resource name of the space. Format: `spaces/`space``
378
373
  # @param [Google::Apis::ChatV1::Space] space_object
@@ -453,8 +448,7 @@ module Google
453
448
  # ALREADY_EXISTS` when setting up a space, try a different `displayName`. An
454
449
  # existing space within the Google Workspace organization might already use this
455
450
  # display name. Requires [user authentication](https://developers.google.com/
456
- # chat/api/guides/auth/users) and the `chat.spaces.create` or `chat.spaces`
457
- # scope.
451
+ # chat/api/guides/auth/users).
458
452
  # @param [Google::Apis::ChatV1::SetUpSpaceRequest] set_up_space_request_object
459
453
  # @param [String] fields
460
454
  # Selector specifying which fields to include in a partial response.
@@ -491,18 +485,16 @@ module Google
491
485
  # policy turned off, then they're invited, and must accept the space invitation
492
486
  # before joining. Otherwise, creating a membership adds the member directly to
493
487
  # the specified space. Requires [user authentication](https://developers.google.
494
- # com/chat/api/guides/auth/users) and the `chat.memberships` (for human
495
- # membership) or `chat.memberships.app` (for app membership) scope. To specify
496
- # the member to add, set the `membership.member.name` in the `
497
- # CreateMembershipRequest`: - To add the calling app to a space or a direct
498
- # message between two human users, use `users/app`. Unable to add other apps to
499
- # the space. - To add a human user, use `users/`user``, where ``user`` can be
500
- # the email address for the user. For users in the same Workspace organization ``
501
- # user`` can also be the ``person_id`` for the person from the People API, or
502
- # the `id` for the user in the Directory API. For example, if the People API
503
- # Person `resourceName` for `user@example.com` is `people/123456789`, you can
504
- # add the user to the space by setting the `membership.member.name` to `users/
505
- # user@example.com` or `users/123456789`.
488
+ # com/chat/api/guides/auth/users). To specify the member to add, set the `
489
+ # membership.member.name` in the `CreateMembershipRequest`: - To add the calling
490
+ # app to a space or a direct message between two human users, use `users/app`.
491
+ # Unable to add other apps to the space. - To add a human user, use `users/`user`
492
+ # `, where ``user`` can be the email address for the user. For users in the same
493
+ # Workspace organization ``user`` can also be the ``person_id`` for the person
494
+ # from the People API, or the `id` for the user in the Directory API. For
495
+ # example, if the People API Person `resourceName` for `user@example.com` is `
496
+ # people/123456789`, you can add the user to the space by setting the `
497
+ # membership.member.name` to `users/user@example.com` or `users/123456789`.
506
498
  # @param [String] parent
507
499
  # Required. The resource name of the space for which to create the membership.
508
500
  # Format: spaces/`space`
@@ -538,8 +530,7 @@ module Google
538
530
 
539
531
  # Deletes a membership. For an example, see [Delete a membership](https://
540
532
  # developers.google.com/chat/api/guides/v1/members/delete). Requires [user
541
- # authentication](https://developers.google.com/chat/api/guides/auth/users) and
542
- # the `chat.memberships` or `chat.memberships.app` authorization scope.
533
+ # authentication](https://developers.google.com/chat/api/guides/auth/users).
543
534
  # @param [String] name
544
535
  # Required. Resource name of the membership to delete. Chat apps can delete
545
536
  # human users' or their own memberships. Chat apps can't delete other apps'
@@ -583,8 +574,7 @@ module Google
583
574
  # supports [service account authentication](https://developers.google.com/chat/
584
575
  # api/guides/auth/service-accounts) and [user authentication](https://developers.
585
576
  # google.com/chat/api/guides/auth/users). [User authentication](https://
586
- # developers.google.com/chat/api/guides/auth/users) requires the `chat.
587
- # memberships` or `chat.memberships.readonly` authorization scope.
577
+ # developers.google.com/chat/api/guides/auth/users).
588
578
  # @param [String] name
589
579
  # Required. Resource name of the membership to retrieve. To get the app's own
590
580
  # membership, you can optionally use `spaces/`space`/members/app`. Format: `
@@ -631,8 +621,7 @@ module Google
631
621
  # Fully supports [service account authentication](https://developers.google.com/
632
622
  # chat/api/guides/auth/service-accounts) and [user authentication](https://
633
623
  # developers.google.com/chat/api/guides/auth/users). [User authentication](https:
634
- # //developers.google.com/chat/api/guides/auth/users) requires the `chat.
635
- # memberships` or `chat.memberships.readonly` authorization scope.
624
+ # //developers.google.com/chat/api/guides/auth/users).
636
625
  # @param [String] parent
637
626
  # Required. The resource name of the space for which to fetch a membership list.
638
627
  # Format: spaces/`space`
@@ -698,19 +687,13 @@ module Google
698
687
  execute_or_queue_command(command, &block)
699
688
  end
700
689
 
701
- # Creates a message. For an example, see [Create a message](https://developers.
702
- # google.com/chat/api/guides/crudl/messages#create_a_message). Requires [
703
- # authentication](https://developers.google.com/chat/api/guides/auth). Creating
704
- # a text message supports both [user authentication](https://developers.google.
705
- # com/chat/api/guides/auth/users) and [app authentication] (https://developers.
706
- # google.com/chat/api/guides/auth/service-accounts). [User authentication](https:
707
- # //developers.google.com/chat/api/guides/auth/users) requires the `chat.
708
- # messages` or `chat.messages.create` authorization scope. Creating a card
709
- # message only supports and requires [app authentication] (https://developers.
710
- # google.com/chat/api/guides/auth/service-accounts). Because Chat provides
711
- # authentication for [webhooks](https://developers.google.com/chat/how-tos/
712
- # webhooks) as part of the URL that's generated when a webhook is registered,
713
- # webhooks can create messages without a service account or user authentication.
690
+ # Creates a message in a Google Chat space. For an example, see [Create a
691
+ # message](https://developers.google.com/chat/api/guides/v1/messages/create).
692
+ # Calling this method requires [authentication](https://developers.google.com/
693
+ # chat/api/guides/auth) and supports the following authentication types: - For
694
+ # text messages, user authentication or app authentication are supported. - For
695
+ # card messages, only app authentication is supported. (Only Chat apps can
696
+ # create card messages.)
714
697
  # @param [String] parent
715
698
  # Required. The resource name of the space in which to create a message. Format:
716
699
  # `spaces/`space``
@@ -779,9 +762,8 @@ module Google
779
762
  # account authentication](https://developers.google.com/chat/api/guides/auth/
780
763
  # service-accounts) and [user authentication](https://developers.google.com/chat/
781
764
  # api/guides/auth/users). [User authentication](https://developers.google.com/
782
- # chat/api/guides/auth/users) requires the `chat.messages` authorization scope.
783
- # Requests authenticated with service accounts can only delete messages created
784
- # by the calling Chat app.
765
+ # chat/api/guides/auth/users). Requests authenticated with service accounts can
766
+ # only delete messages created by the calling Chat app.
785
767
  # @param [String] name
786
768
  # Required. Resource name of the message that you want to delete, in the form `
787
769
  # spaces/*/messages/*` Example: `spaces/AAAAAAAAAAA/messages/BBBBBBBBBBB.
@@ -826,9 +808,8 @@ module Google
826
808
  # supports [service account authentication](https://developers.google.com/chat/
827
809
  # api/guides/auth/service-accounts) and [user authentication](https://developers.
828
810
  # google.com/chat/api/guides/auth/users). [User authentication](https://
829
- # developers.google.com/chat/api/guides/auth/users) requires the `chat.messages`
830
- # or `chat.messages.readonly` authorization scope. Note: Might return a message
831
- # from a blocked member or space.
811
+ # developers.google.com/chat/api/guides/auth/users). Note: Might return a
812
+ # message from a blocked member or space.
832
813
  # @param [String] name
833
814
  # Required. Resource name of the message to retrieve. Format: `spaces/`space`/
834
815
  # messages/`message`` If the message begins with `client-`, then it has a custom
@@ -866,8 +847,7 @@ module Google
866
847
  # Lists messages in a space that the caller is a member of, including messages
867
848
  # from blocked members and spaces. For an example, see [List messages](/chat/api/
868
849
  # guides/v1/messages/list). Requires [user authentication](https://developers.
869
- # google.com/chat/api/guides/auth/users) and the `chat.messages` or `chat.
870
- # messages.readonly` authorization scope.
850
+ # google.com/chat/api/guides/auth/users).
871
851
  # @param [String] parent
872
852
  # Required. The resource name of the space to list messages from. Format: `
873
853
  # spaces/`space``
@@ -948,9 +928,9 @@ module Google
948
928
  # api/guides/auth). Fully supports [service account authentication](https://
949
929
  # developers.google.com/chat/api/guides/auth/service-accounts) and [user
950
930
  # authentication](https://developers.google.com/chat/api/guides/auth/users). [
951
- # User authentication](https://developers.google.com/chat/api/guides/auth/users)
952
- # requires the `chat.messages` authorization scope. Requests authenticated with
953
- # service accounts can only update messages created by the calling Chat app.
931
+ # User authentication](https://developers.google.com/chat/api/guides/auth/users).
932
+ # Requests authenticated with service accounts can only update messages created
933
+ # by the calling Chat app.
954
934
  # @param [String] name
955
935
  # Resource name in the form `spaces/*/messages/*`. Example: `spaces/AAAAAAAAAAA/
956
936
  # messages/BBBBBBBBBBB.BBBBBBBBBBB`
@@ -1005,9 +985,9 @@ module Google
1005
985
  # api/guides/auth). Fully supports [service account authentication](https://
1006
986
  # developers.google.com/chat/api/guides/auth/service-accounts) and [user
1007
987
  # authentication](https://developers.google.com/chat/api/guides/auth/users). [
1008
- # User authentication](https://developers.google.com/chat/api/guides/auth/users)
1009
- # requires the `chat.messages` authorization scope. Requests authenticated with
1010
- # service accounts can only update messages created by the calling Chat app.
988
+ # User authentication](https://developers.google.com/chat/api/guides/auth/users).
989
+ # Requests authenticated with service accounts can only update messages created
990
+ # by the calling Chat app.
1011
991
  # @param [String] name
1012
992
  # Resource name in the form `spaces/*/messages/*`. Example: `spaces/AAAAAAAAAAA/
1013
993
  # messages/BBBBBBBBBBB.BBBBBBBBBBB`
@@ -1093,8 +1073,7 @@ module Google
1093
1073
  # Creates a reaction and adds it to a message. For an example, see [Create a
1094
1074
  # reaction](https://developers.google.com/chat/api/guides/v1/reactions/create).
1095
1075
  # Requires [user authentication](https://developers.google.com/chat/api/guides/
1096
- # auth/users) and the `chat.messages`, `chat.messages.reactions`, or `chat.
1097
- # messages.reactions.create` scope. Only unicode emoji are supported.
1076
+ # auth/users). Only unicode emoji are supported.
1098
1077
  # @param [String] parent
1099
1078
  # Required. The message where the reaction is created. Format: `spaces/`space`/
1100
1079
  # messages/`message``
@@ -1130,8 +1109,7 @@ module Google
1130
1109
 
1131
1110
  # Deletes a reaction to a message. For an example, see [Delete a reaction](https:
1132
1111
  # //developers.google.com/chat/api/guides/v1/reactions/delete). Requires [user
1133
- # authentication](https://developers.google.com/chat/api/guides/auth/users) and
1134
- # the `chat.messages` or `chat.messages.reactions` scope.
1112
+ # authentication](https://developers.google.com/chat/api/guides/auth/users).
1135
1113
  # @param [String] name
1136
1114
  # Required. Name of the reaction to delete. Format: `spaces/`space`/messages/`
1137
1115
  # message`/reactions/`reaction``
@@ -1164,9 +1142,7 @@ module Google
1164
1142
 
1165
1143
  # Lists reactions to a message. For an example, see [List reactions](https://
1166
1144
  # developers.google.com/chat/api/guides/v1/reactions/list). Requires [user
1167
- # authentication](https://developers.google.com/chat/api/guides/auth/users) and `
1168
- # chat.messages`, `chat.messages.readonly`, `chat.messages.reactions`, or `chat.
1169
- # messages.reactions.readonly` scope.
1145
+ # authentication](https://developers.google.com/chat/api/guides/auth/users).
1170
1146
  # @param [String] parent
1171
1147
  # Required. The message users reacted to. Format: `spaces/`space`/messages/`
1172
1148
  # message``
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-apis-chat_v1
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.68.0
4
+ version: 0.69.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Google LLC
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2023-08-13 00:00:00.000000000 Z
11
+ date: 2023-08-27 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: google-apis-core
@@ -58,7 +58,7 @@ licenses:
58
58
  metadata:
59
59
  bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
60
60
  changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-chat_v1/CHANGELOG.md
61
- documentation_uri: https://googleapis.dev/ruby/google-apis-chat_v1/v0.68.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-chat_v1/v0.69.0
62
62
  source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-chat_v1
63
63
  post_install_message:
64
64
  rdoc_options: []
@@ -75,7 +75,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
75
75
  - !ruby/object:Gem::Version
76
76
  version: '0'
77
77
  requirements: []
78
- rubygems_version: 3.4.2
78
+ rubygems_version: 3.4.19
79
79
  signing_key:
80
80
  specification_version: 4
81
81
  summary: Simple REST client for Google Chat API V1