Add flight time editing and manual entry with yyyy-mm-dd date format

[Copilot]

Users need to correct flight times when data is inaccurate and manually enter flight details when searches return no results.

Changes

Time Editing

• Clock icon (🕒) next to each flight opens modal with text inputs
• Date format: yyyy-mm-dd hh:mm (24-hour time, space separator)
• Custom times passed to backend via hidden form fields and applied during iCal generation
• Client-side validation ensures departure precedes arrival
• Pattern validation enforces correct format

Manual Entry

• "Enter Flight Details Manually" button surfaces when flight lookup fails
• Form captures: flight number, airline, airports/codes, times, timezones
• Date format: yyyy-mm-dd hh:mm (24-hour time, space separator)
• Server validates airport codes (3 uppercase letters), datetime formats, and required fields
• New make_ics_from_manual_data() handles yyyy-mm-dd hh:mm format

Date Format Standardization

• All date/datetime inputs use yyyy-mm-dd format (never mm/dd/yyyy)
• Text inputs with pattern validation replace HTML5 date/datetime-local inputs
• Clear placeholders guide users on expected format
• Homepage flight date: yyyy-mm-dd
• Manual entry and time edit modal: yyyy-mm-dd hh:mm

Technical improvements

• HTML5 DOCTYPE declarations added to all templates
• UTC timestamps for iCal dtstamp fields
• Import organization (moved re to top-level imports)
• Backend datetime parsing updated to handle yyyy-mm-dd hh:mm format

Screenshots

Homepage with yyyy-mm-dd format

Manual entry form with yyyy-mm-dd hh:mm format

Time edit modal with yyyy-mm-dd hh:mm format

Implementation Note

Existing make_ical_event() expects YYYYMMDD HHMM format from flight API, while make_ics_from_manual_data() accepts YYYY-MM-DD HH:MM from text inputs with pattern validation. Both convert to timezone-aware datetime objects before iCal generation.

Original prompt

I need you to create a PR which allows you to edit the timing of a flight if the times are wrong, maybe if the flights are found there's a clock icon next to it which brings a time changing pop up. Also allow for an option to manually input the details of no flight is found for the inputted flight code - everything that's needed. Keep the design and feel the same throughout

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[mschmid09]

use date format yyyy-mm-dd for inputs never mm/dd/yyyy @copilot

[Copilot]

use date format yyyy-mm-dd for inputs never mm/dd/yyyy @copilot

Done! Changed all date inputs to use yyyy-mm-dd format (never mm/dd/yyyy). All datetime inputs now show yyyy-mm-dd hh:mm format with clear placeholders and pattern validation. (01a8c8e)

Updated formats:

• Homepage flight date: yyyy-mm-dd
• Manual entry times: yyyy-mm-dd hh:mm
• Time edit modal: yyyy-mm-dd hh:mm

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.flightradar24.com
  • Triggering command: /usr/bin/python python app.py (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)