Skip to content

Commit d9b9556

Browse files
feat: Automated regeneration of Dialogflow client (googleapis#12588)
Auto-created at 2024-11-21 13:17:15 +0000 using the toys pull request generator.
1 parent 36855a8 commit d9b9556

18 files changed

+21
-21
lines changed

clients/dialogflow/lib/google_api/dialogflow/v2/api/projects.ex

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6587,7 +6587,7 @@ defmodule GoogleApi.Dialogflow.V2.Api.Projects do
65876587
end
65886588

65896589
@doc """
6590-
Creates a conversation profile in the specified project. ConversationProfile.CreateTime and ConversationProfile.UpdateTime aren't populated in the response. You can retrieve them via GetConversationProfile API.
6590+
Creates a conversation profile in the specified project. ConversationProfile.create_time and ConversationProfile.update_time aren't populated in the response. You can retrieve them via GetConversationProfile API.
65916591

65926592
## Parameters
65936593

@@ -6886,7 +6886,7 @@ defmodule GoogleApi.Dialogflow.V2.Api.Projects do
68866886
end
68876887

68886888
@doc """
6889-
Updates the specified conversation profile. ConversationProfile.CreateTime and ConversationProfile.UpdateTime aren't populated in the response. You can retrieve them via GetConversationProfile API.
6889+
Updates the specified conversation profile. ConversationProfile.create_time and ConversationProfile.update_time aren't populated in the response. You can retrieve them via GetConversationProfile API.
68906890

68916891
## Parameters
68926892

@@ -15615,7 +15615,7 @@ defmodule GoogleApi.Dialogflow.V2.Api.Projects do
1561515615
end
1561615616

1561715617
@doc """
15618-
Creates a conversation profile in the specified project. ConversationProfile.CreateTime and ConversationProfile.UpdateTime aren't populated in the response. You can retrieve them via GetConversationProfile API.
15618+
Creates a conversation profile in the specified project. ConversationProfile.create_time and ConversationProfile.update_time aren't populated in the response. You can retrieve them via GetConversationProfile API.
1561915619

1562015620
## Parameters
1562115621

@@ -15914,7 +15914,7 @@ defmodule GoogleApi.Dialogflow.V2.Api.Projects do
1591415914
end
1591515915

1591615916
@doc """
15917-
Updates the specified conversation profile. ConversationProfile.CreateTime and ConversationProfile.UpdateTime aren't populated in the response. You can retrieve them via GetConversationProfile API.
15917+
Updates the specified conversation profile. ConversationProfile.create_time and ConversationProfile.update_time aren't populated in the response. You can retrieve them via GetConversationProfile API.
1591815918

1591915919
## Parameters
1592015920

clients/dialogflow/lib/google_api/dialogflow/v2/metadata.ex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ defmodule GoogleApi.Dialogflow.V2 do
2020
API client metadata for GoogleApi.Dialogflow.V2.
2121
"""
2222

23-
@discovery_revision "20241019"
23+
@discovery_revision "20241119"
2424

2525
def discovery_revision(), do: @discovery_revision
2626
end

clients/dialogflow/lib/google_api/dialogflow/v2/model/google_cloud_dialogflow_cx_v3_barge_in_config.ex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717

1818
defmodule GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowCxV3BargeInConfig do
1919
@moduledoc """
20-
Configuration of the barge-in behavior. Barge-in instructs the API to return a detected utterance at a proper time while the client is playing back the response audio from a previous request. When the client sees the utterance, it should stop the playback and immediately get ready for receiving the responses for the current request. The barge-in handling requires the client to start streaming audio input as soon as it starts playing back the audio from the previous response. The playback is modeled into two phases: * No barge-in phase: which goes first and during which speech detection should not be carried out. * Barge-in phase: which follows the no barge-in phase and during which the API starts speech detection and may inform the client that an utterance has been detected. Note that no-speech event is not expected in this phase. The client provides this configuration in terms of the durations of those two phases. The durations are measured in terms of the audio length from the the start of the input audio. No-speech event is a response with END_OF_UTTERANCE without any transcript following up.
20+
Configuration of the barge-in behavior. Barge-in instructs the API to return a detected utterance at a proper time while the client is playing back the response audio from a previous request. When the client sees the utterance, it should stop the playback and immediately get ready for receiving the responses for the current request. The barge-in handling requires the client to start streaming audio input as soon as it starts playing back the audio from the previous response. The playback is modeled into two phases: * No barge-in phase: which goes first and during which speech detection should not be carried out. * Barge-in phase: which follows the no barge-in phase and during which the API starts speech detection and may inform the client that an utterance has been detected. Note that no-speech event is not expected in this phase. The client provides this configuration in terms of the durations of those two phases. The durations are measured in terms of the audio length from the start of the input audio. No-speech event is a response with END_OF_UTTERANCE without any transcript following up.
2121
2222
## Attributes
2323

clients/dialogflow/lib/google_api/dialogflow/v2/model/google_cloud_dialogflow_cx_v3beta1_barge_in_config.ex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717

1818
defmodule GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowCxV3beta1BargeInConfig do
1919
@moduledoc """
20-
Configuration of the barge-in behavior. Barge-in instructs the API to return a detected utterance at a proper time while the client is playing back the response audio from a previous request. When the client sees the utterance, it should stop the playback and immediately get ready for receiving the responses for the current request. The barge-in handling requires the client to start streaming audio input as soon as it starts playing back the audio from the previous response. The playback is modeled into two phases: * No barge-in phase: which goes first and during which speech detection should not be carried out. * Barge-in phase: which follows the no barge-in phase and during which the API starts speech detection and may inform the client that an utterance has been detected. Note that no-speech event is not expected in this phase. The client provides this configuration in terms of the durations of those two phases. The durations are measured in terms of the audio length from the the start of the input audio. No-speech event is a response with END_OF_UTTERANCE without any transcript following up.
20+
Configuration of the barge-in behavior. Barge-in instructs the API to return a detected utterance at a proper time while the client is playing back the response audio from a previous request. When the client sees the utterance, it should stop the playback and immediately get ready for receiving the responses for the current request. The barge-in handling requires the client to start streaming audio input as soon as it starts playing back the audio from the previous response. The playback is modeled into two phases: * No barge-in phase: which goes first and during which speech detection should not be carried out. * Barge-in phase: which follows the no barge-in phase and during which the API starts speech detection and may inform the client that an utterance has been detected. Note that no-speech event is not expected in this phase. The client provides this configuration in terms of the durations of those two phases. The durations are measured in terms of the audio length from the start of the input audio. No-speech event is a response with END_OF_UTTERANCE without any transcript following up.
2121
2222
## Attributes
2323

clients/dialogflow/lib/google_api/dialogflow/v2/model/google_cloud_dialogflow_v2_analyze_content_response.ex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ defmodule GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowV2AnalyzeContentRes
2121
2222
## Attributes
2323
24-
* `automatedAgentReply` (*type:* `GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowV2AutomatedAgentReply.t`, *default:* `nil`) - Only set if a Dialogflow automated agent has responded. Note that: AutomatedAgentReply.detect_intent_response.output_audio and AutomatedAgentReply.detect_intent_response.output_audio_config are always empty, use reply_audio instead.
24+
* `automatedAgentReply` (*type:* `GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowV2AutomatedAgentReply.t`, *default:* `nil`) - Only set if a Dialogflow automated agent has responded. Note that in AutomatedAgentReply.DetectIntentResponse, Sessions.DetectIntentResponse.output_audio and Sessions.DetectIntentResponse.output_audio_config are always empty, use reply_audio instead.
2525
* `dtmfParameters` (*type:* `GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowV2DtmfParameters.t`, *default:* `nil`) - Indicates the parameters of DTMF.
2626
* `endUserSuggestionResults` (*type:* `list(GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowV2SuggestionResult.t)`, *default:* `nil`) - The suggestions for end user. The order is the same as HumanAgentAssistantConfig.SuggestionConfig.feature_configs of HumanAgentAssistantConfig.end_user_suggestion_config. Same as human_agent_suggestion_results, any failure of Agent Assist features will not lead to the overall failure of an AnalyzeContent API call. Instead, the features will fail silently with the error field set in the corresponding SuggestionResult.
2727
* `humanAgentSuggestionResults` (*type:* `list(GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowV2SuggestionResult.t)`, *default:* `nil`) - The suggestions for most recent human agent. The order is the same as HumanAgentAssistantConfig.SuggestionConfig.feature_configs of HumanAgentAssistantConfig.human_agent_suggestion_config. Note that any failure of Agent Assist features will not lead to the overall failure of an AnalyzeContent API call. Instead, the features will fail silently with the error field set in the corresponding SuggestionResult.

clients/dialogflow/lib/google_api/dialogflow/v2/model/google_cloud_dialogflow_v2_answer_record.ex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717

1818
defmodule GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowV2AnswerRecord do
1919
@moduledoc """
20-
Answer records are records to manage answer history and feedbacks for Dialogflow. Currently, answer record includes: - human agent assistant article suggestion - human agent assistant faq article It doesn't include: - `DetectIntent` intent matching - `DetectIntent` knowledge Answer records are not related to the conversation history in the Dialogflow Console. A Record is generated even when the end-user disables conversation history in the console. Records are created when there's a human agent assistant suggestion generated. A typical workflow for customers provide feedback to an answer is: 1. For human agent assistant, customers get suggestion via ListSuggestions API. Together with the answers, AnswerRecord.name are returned to the customers. 2. The customer uses the AnswerRecord.name to call the UpdateAnswerRecord method to send feedback about a specific answer that they believe is wrong.
20+
Answer records are records to manage answer history and feedbacks for Dialogflow. Currently, answer record includes: - human agent assistant article suggestion - human agent assistant faq article It doesn't include: - `DetectIntent` intent matching - `DetectIntent` knowledge Answer records are not related to the conversation history in the Dialogflow Console. A Record is generated even when the end-user disables conversation history in the console. Records are created when there's a human agent assistant suggestion generated. A typical workflow for customers provide feedback to an answer is: 1. For human agent assistant, customers get suggestion via ListSuggestions API. Together with the answers, AnswerRecord.name are returned to the customers. 2. The customer uses the AnswerRecord.name to call the AnswerRecords.UpdateAnswerRecord method to send feedback about a specific answer that they believe is wrong.
2121
2222
## Attributes
2323

clients/dialogflow/lib/google_api/dialogflow/v2/model/google_cloud_dialogflow_v2_clear_suggestion_feature_config_operation_metadata.ex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717

1818
defmodule GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowV2ClearSuggestionFeatureConfigOperationMetadata do
1919
@moduledoc """
20-
Metadata for a ConversationProfile.ClearSuggestionFeatureConfig operation.
20+
Metadata for a ConversationProfiles.ClearSuggestionFeatureConfig operation.
2121
2222
## Attributes
2323

clients/dialogflow/lib/google_api/dialogflow/v2/model/google_cloud_dialogflow_v2_clear_suggestion_feature_config_request.ex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717

1818
defmodule GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowV2ClearSuggestionFeatureConfigRequest do
1919
@moduledoc """
20-
The request message for ConversationProfiles.ClearFeature.
20+
The request message for ConversationProfiles.ClearSuggestionFeatureConfig.
2121
2222
## Attributes
2323

clients/dialogflow/lib/google_api/dialogflow/v2/model/google_cloud_dialogflow_v2_create_conversation_dataset_operation_metadata.ex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717

1818
defmodule GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowV2CreateConversationDatasetOperationMetadata do
1919
@moduledoc """
20-
Metadata for ConversationDatasets.
20+
Metadata for CreateConversationDataset.
2121
2222
## Attributes
2323

clients/dialogflow/lib/google_api/dialogflow/v2/model/google_cloud_dialogflow_v2_delete_conversation_dataset_operation_metadata.ex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717

1818
defmodule GoogleApi.Dialogflow.V2.Model.GoogleCloudDialogflowV2DeleteConversationDatasetOperationMetadata do
1919
@moduledoc """
20-
Metadata for ConversationDatasets.
20+
Metadata for DeleteConversationDataset.
2121
2222
## Attributes
2323

0 commit comments

Comments
 (0)