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.
For the most up to date information on UI development browser support
$ npm i @aurodesignsystem/auro-flightlineThe use of any Auro custom element has a dependency on the Auro Design Tokens.
Defining the component dependency within each component that is using the <auro-flightline> component.
import "@aurodesignsystem/auro-flightline";Reference component in HTML
<auro-flightline></auro-flightline>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>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.
<auro-flightline></auro-flightline>In order to develop against this project, if you are not part of the core team, you will be required to fork the project prior to submitting a pull request.
Please be sure to review the contribution guidelines for this project. Please make sure to pay special attention to the conventional commits section of the document.
Once the project has been cloned to your local resource and you have installed all the dependencies you will need to open a shell session to run the dev server.
$ npm run devOpen localhost:8000
Automated tests are required for every Auro component. See .\test\auro-flightline.test.js for the tests for this component. Run npm run test to run the tests and check code coverage. Tests must pass and meet a certain coverage threshold to commit. See the testing documentation for more details.