Skip to content

Commit 9457c42

Browse files
feat: Automated regeneration of Dialogflow client (googleapis#12624)
Auto-created at 2024-11-27 13:20:09 +0000 using the toys pull request generator.
1 parent 60b1121 commit 9457c42

9 files changed

+9
-9
lines changed

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

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

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

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

clients/dialogflow/lib/google_api/dialogflow/v3/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.V3.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/v3/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.V3.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/v3/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.V3.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/v3/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.V3.Model.GoogleCloudDialogflowV2CreateConversationDatasetOperationMetadata do
1919
@moduledoc """
20-
Metadata for ConversationDatasets.
20+
Metadata for CreateConversationDataset.
2121
2222
## Attributes
2323

clients/dialogflow/lib/google_api/dialogflow/v3/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.V3.Model.GoogleCloudDialogflowV2DeleteConversationDatasetOperationMetadata do
1919
@moduledoc """
20-
Metadata for ConversationDatasets.
20+
Metadata for DeleteConversationDataset.
2121
2222
## Attributes
2323

clients/dialogflow/lib/google_api/dialogflow/v3/model/google_cloud_dialogflow_v2_sentiment_analysis_result.ex

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

1818
defmodule GoogleApi.Dialogflow.V3.Model.GoogleCloudDialogflowV2SentimentAnalysisResult do
1919
@moduledoc """
20-
The result of sentiment analysis. Sentiment analysis inspects user input and identifies the prevailing subjective opinion, especially to determine a user's attitude as positive, negative, or neutral. For Participants.DetectIntent, it needs to be configured in DetectIntentRequest.query_params. For Participants.StreamingDetectIntent, it needs to be configured in StreamingDetectIntentRequest.query_params. And for Participants.AnalyzeContent and Participants.StreamingAnalyzeContent, it needs to be configured in ConversationProfile.human_agent_assistant_config
20+
The result of sentiment analysis. Sentiment analysis inspects user input and identifies the prevailing subjective opinion, especially to determine a user's attitude as positive, negative, or neutral. For DetectIntent, it needs to be configured in DetectIntentRequest.query_params. For StreamingDetectIntent, it needs to be configured in StreamingDetectIntentRequest.query_params. And for Participants.AnalyzeContent and Participants.StreamingAnalyzeContent, it needs to be configured in ConversationProfile.human_agent_assistant_config
2121
2222
## Attributes
2323

clients/dialogflow/lib/google_api/dialogflow/v3/model/google_cloud_dialogflow_v2_set_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.V3.Model.GoogleCloudDialogflowV2SetSuggestionFeatureConfigOperationMetadata do
1919
@moduledoc """
20-
Metadata for a ConversationProfile.SetSuggestionFeatureConfig operation.
20+
Metadata for a ConversationProfiles.SetSuggestionFeatureConfig operation.
2121
2222
## Attributes
2323

clients/dialogflow/mix.exs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@
1818
defmodule GoogleApi.Dialogflow.Mixfile do
1919
use Mix.Project
2020

21-
@version "0.88.1"
21+
@version "0.88.2"
2222

2323
def project() do
2424
[

0 commit comments

Comments
 (0)