Struct SegmentInfo 

pub struct SegmentInfo {
    pub booking_code: Option<String>,
    pub booking_code_count: Option<i32>,
    pub cabin: Option<String>,
    pub connection_duration: Option<i32>,
    pub duration: Option<i32>,
    pub flight: Option<FlightInfo>,
    pub id: Option<String>,
    pub kind: Option<String>,
    pub leg: Option<Vec<LegInfo>>,
    pub married_segment_group: Option<String>,
    pub subject_to_government_approval: Option<bool>,
}

Details of a segment of a flight; a segment is one or more consecutive legs on the same flight. For example a hypothetical flight ZZ001, from DFW to OGG, would have one segment with two legs: DFW to HNL (leg 1), HNL to OGG (leg 2), and DFW to OGG (legs 1 and 2).

This type is not used in any activity, and only used as part of another schema.

Fields

booking_code: Option<String>

The booking code or class for this segment.

booking_code_count: Option<i32>

The number of seats available in this booking code on this segment.

cabin: Option<String>

The cabin booked for this segment.

connection_duration: Option<i32>

In minutes, the duration of the connection following this segment.

duration: Option<i32>

The duration of the flight segment in minutes.

flight: Option<FlightInfo>

The flight this is a segment of.

id: Option<String>

An id uniquely identifying the segment in the solution.

kind: Option<String>

Identifies this as a segment object. A segment is one or more consecutive legs on the same flight. For example a hypothetical flight ZZ001, from DFW to OGG, could have one segment with two legs: DFW to HNL (leg 1), HNL to OGG (leg 2). Value: the fixed string qpxexpress#segmentInfo.

leg: Option<Vec<LegInfo>>

The legs composing this segment.

married_segment_group: Option<String>

The solution-based index of a segment in a married segment group. Married segments can only be booked together. For example, an airline might report a certain booking code as sold out from Boston to Pittsburgh, but as available as part of two married segments Boston to Chicago connecting through Pittsburgh. For example content of this field, consider the round-trip flight ZZ1 PHX-PHL ZZ2 PHL-CLT ZZ3 CLT-PHX. This has three segments, with the two outbound ones (ZZ1 ZZ2) married. In this case, the two outbound segments belong to married segment group 0, and the return segment belongs to married segment group 1.

subject_to_government_approval: Option<bool>

Whether the operation of this segment remains subject to government approval.

Trait Implementations

impl Clone for SegmentInfo

fn clone(&self) -> SegmentInfo

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for SegmentInfo

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for SegmentInfo

fn default() -> SegmentInfo

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for SegmentInfo

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for SegmentInfo

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl Part for SegmentInfo