Skip to content

feat(card): square map view & configurable flight list position - #40

Open
Springvar wants to merge 11 commits into
mainfrom
feat/square-map-and-list-position
Open

feat(card): square map view & configurable flight list position#40
Springvar wants to merge 11 commits into
mainfrom
feat/square-map-and-list-position

Conversation

@Springvar

Copy link
Copy Markdown
Owner

Summary

Adds a square map view option and a configurable flight list position, and fixes the pre-existing tsc / lint failures so they pass cleanly.

Features

  • radar.view: 'radar' | 'map' (default radar)
    • map renders a full-bleed square Leaflet map instead of the circular radar screen — better for fullscreen and multi-column layouts.
    • Automatically falls back to system tiles when no background_map is chosen.
    • New radar.rings setting to control radar grid rings/bearing lines (default off in map view, on in radar view; overridable).
  • list.position: 'below' | 'left' | 'right' (default below)
    • Places the flight list beside the radar/map on wide cards.
    • Falls back to below automatically when the card is too narrow (< ~560px) via CSS container queries — adapts dynamically, no config changes.

Fixes (pre-existing)

  • Typecheck errors down from 11 → 0 (missing invalidateSize, _currentMapConfig, LeafletMapOptions.zoomSnap, editor aircraft-marker indexing, browser test cast, vitest.browser.config.ts launchlaunchOptions).
  • Lint errors down from 24 → 0 (excluded the generated build bundle from linting).
  • New editor UI for all the above options + README docs.

Verification

  • tsc --noEmit: 0 errors
  • eslint .: 0 errors
  • vitest run: 196 tests pass
  • vite build: succeeds

- Add radar.view 'map' option for a full-bleed square map view (falls back to system tiles, hides rings by default with radar.rings override)
- Add list.position 'below'|'left'|'right' with CSS container-query fallback to below on narrow cards
- Fix pre-existing typecheck and lint issues so tsc and yarn lint pass cleanly
The guarded alias registered 'flightradar24-card' whenever the name was
free, but a custom element type can only be registered once. If this
card loaded before the Flightradar24 integration's built-in card, the
alias claimed the name and the integration's card failed with
"the name flightradar24-card has already been used" on every load
(issue #41). This card now only registers flightradar24-radar-card.

Refs #39, #41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant