Skip to content
GitLab
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Changes
Page history
Spargonaut created page: Checklist Formatting Rules
authored
Aug 24, 2018
by
james spargo
Show whitespace changes
Inline
Side-by-side
Checklist-Formatting-Rules.md
0 → 100644
View page @
afa2b0c1
The following is an explanation of the way FOSSFlight Checklists are parsed when imported.
#### Basic file format and file extension
The file is expected to be formatted in a CSV format, with a file extension of
`.csv`
This is done to facilitate checklist creation and customizations being done using your favorite spreadsheet application.
A FOSSFlight checklist file is expected to contain checklists for one aircraft.
A FOSSFlight checklist file can contain numerous checklists.
Each row of the csv file is expected to have at least one comma. Rows missing a comma will be ignored.
#### Tail Number
The parser attempts to apply the filename as the tail number. This can easily be corrected after the checklists are imported.
#### Checklist Name and Type
A Checklist is identified by the string in the second column ending with the word ' checklist' ([space]checklist)
The type of the checklist is indicated by the word proceeding the word 'checklist'.
For example... 'Standard Checklist'
The name of the checklist is identified by the string, in the first column, of the same row where the second column identifies the checklist type.
#### Checklist Items
Each Checklist item line should contain only one comma. Text after the second token will be ignored.
The text before the comma is the Checklist Item Name.
The text after the comma is the Checklist Item Action.
#### End of the Checklist
Each checklist should end with a blank row