Flightline

The <auro-flightline> component represents any layovers and/or stopovers a guest may encounter throughout their journey.

For mobile, the number of stops is automatically calculated by the number of layovers and/or stopovers added in the DOM via the auro-flight-segment element.

Use Cases

The <auro-flightline> element should be used in situations where users may:

• Flying from SEA (Seattle, WA) to AVP (Scranton, PA) will require a layover in ORD (Chicago, IL)
• Flying from ANC (Anchorage, AK) to ADK (Adak Island, AK) will have a stopover in CDB (Cold Bay, AK). These passengers will not deplane in Cold Bay. Stopover duration cannot be predicted due to variants in passenger and cargo loads.

Install

$ npm i @aurodesignsystem/auro-flightline

Define Dependency in Project

Defining the dependency within each project that is using the <auro-flightline> component.

import "@aurodesignsystem/auro-flightline";

Use CDN

In cases where the project is not able to process JS assets, there are pre-processed assets available for use. Legacy browsers such as IE11 are no longer supported.

<script type="module" src="https://cdn.jsdelivr.net/npm/@aurodesignsystem/auro-flightline@latest/+esm"></script>

Basic Example

<auro-flightline></auro-flightline>

Custom Component Registration for Version Management

There are two key parts to every Auro component: the class and the custom element definition. The class defines the component’s behavior, while the custom element registers it under a specific name so it can be used in HTML.

When you install the component as described on the Install page, the class is imported automatically, and the component is registered globally for you.

However, if you need to load multiple versions of the same component on a single page (for example, when two projects depend on different versions), you can manually register the class under a custom element name to avoid conflicts.

You can do this by importing only the component class and using the register(name) method with a unique name:

// Import the class only
import { AuroFlightSegment } from "./auro-flight-segment.js";
import { AuroFlightline } from "./auro-flightline.js";

// Register with a custom name if desired
AuroFlightSegment.register('custom-flight-segment');
AuroFlightline.register('custom-flightline');

This will create a new custom element <custom-flightline> and <custom-flight-segment> that behaves exactly like <auro-flightline> and <auro-flight-segment>, allowing both sets of components to coexist on the same page without interfering with each other.

<custom-flightline>
    <custom-flight-segment canceled iata="ORD" duration="3h 40m"></custom-flight-segment>
</custom-flightline>