Skip to content

Commit

Permalink
docs: clarify behavior of UpdateDeliveryVehicle
Browse files Browse the repository at this point in the history
PiperOrigin-RevId: 651102275

Source-Link: googleapis/googleapis@ecbfd84

Source-Link: googleapis/googleapis-gen@6e1d816
Copy-Tag: eyJwIjoiYXBpcy9Hb29nbGUuTWFwcy5GbGVldEVuZ2luZS5EZWxpdmVyeS5WMS8uT3dsQm90LnlhbWwiLCJoIjoiNmUxZDgxNjUxZDk2YTI5MTI1NmI4ZmE0MmZiZjNkNTBjYTFjOGQ5NCJ9
  • Loading branch information
gcf-owl-bot[bot] authored and amanda-tarafa committed Jul 10, 2024
1 parent bb34cc0 commit 4acca65
Show file tree
Hide file tree
Showing 2 changed files with 39 additions and 39 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -213,9 +213,9 @@ public abstract partial class DeliveryServiceBase
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand Down Expand Up @@ -440,9 +440,9 @@ protected DeliveryServiceClient(ClientBaseConfiguration configuration) : base(co
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand All @@ -459,9 +459,9 @@ protected DeliveryServiceClient(ClientBaseConfiguration configuration) : base(co
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand All @@ -476,9 +476,9 @@ protected DeliveryServiceClient(ClientBaseConfiguration configuration) : base(co
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand All @@ -495,9 +495,9 @@ protected DeliveryServiceClient(ClientBaseConfiguration configuration) : base(co
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -647,9 +647,9 @@ public virtual DeliveryVehicle GetDeliveryVehicle(DeliveryVehicleName name, gaxg
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand All @@ -662,9 +662,9 @@ public virtual DeliveryVehicle UpdateDeliveryVehicle(UpdateDeliveryVehicleReques
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand All @@ -677,9 +677,9 @@ public virtual DeliveryVehicle UpdateDeliveryVehicle(UpdateDeliveryVehicleReques
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand All @@ -692,9 +692,9 @@ public virtual DeliveryVehicle UpdateDeliveryVehicle(UpdateDeliveryVehicleReques
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand All @@ -721,9 +721,9 @@ public virtual DeliveryVehicle UpdateDeliveryVehicle(DeliveryVehicle deliveryVeh
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand All @@ -750,9 +750,9 @@ public virtual DeliveryVehicle UpdateDeliveryVehicle(DeliveryVehicle deliveryVeh
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand Down Expand Up @@ -1750,9 +1750,9 @@ public override DeliveryVehicle GetDeliveryVehicle(GetDeliveryVehicleRequest req
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand All @@ -1768,9 +1768,9 @@ public override DeliveryVehicle UpdateDeliveryVehicle(UpdateDeliveryVehicleReque
/// <summary>
/// Writes updated `DeliveryVehicle` data to Fleet Engine, and assigns
/// `Tasks` to the `DeliveryVehicle`. You cannot update the name of the
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`
/// though, but it must contain all of the `VehicleJourneySegment`s currently
/// on the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `DeliveryVehicle`. You *can* update `remaining_vehicle_journey_segments`,
/// but it must contain all of the `VehicleJourneySegment`s to be persisted on
/// the `DeliveryVehicle`. The `task_id`s are retrieved from
/// `remaining_vehicle_journey_segments`, and their corresponding `Tasks` are
/// assigned to the `DeliveryVehicle` if they have not yet been assigned.
/// </summary>
Expand Down

0 comments on commit 4acca65

Please sign in to comment.