@meri-imperiumi/signalk-passage-briefing 0.12.2 → 0.12.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,8 @@
|
|
|
2
2
|
|
|
3
3
|
## [Unreleased]
|
|
4
4
|
|
|
5
|
+
## [0.12.3] - 2026-10-16
|
|
6
|
+
|
|
5
7
|
## [0.12.2] - 2026-10-16
|
|
6
8
|
|
|
7
9
|
### Changed
|
|
@@ -9,7 +11,7 @@
|
|
|
9
11
|
|
|
10
12
|
### Fixed
|
|
11
13
|
- The webapp console logged three requests that could never succeed (work doc #40/#30 session report): the "Next" compile pill and the sea-legs day checkpoints called `/api/api/status` and `/api/api/sea-legs` — a stray `api/` segment doubled into the plugin base ever since those two UI pieces shipped, 404ing on every load and silently hiding both features. The URLs now match the registered routes. The critical-hazard banner polled the Signal K REST notifications subtree (`vessels/self/notifications/navigation/briefing/hazards`), which 404s whenever no notification was ever raised on the server; the escalation's active list now also serves from the plugin's own `GET /api/hazards/active` (same data the delta stream carries, empty list when nominal) and the banner polls that.
|
|
12
|
-
- The route briefing had no manual refresh affordance on a fresh cache: the "Update now" button only existed in the no-cached strip and the outdated banner, so the crew couldn't regenerate an up-to-date-looking briefing (e.g. to pick up the throttled payload shape or a fresher forecast) — while conditions-here always carried its card-head button. The tactical view's "Next 24 Hours" card head now carries the same "Update now" in the same place, wired to the route refresh and disabled offline like its here-mode twin.
|
|
14
|
+
- The route briefing had no manual refresh affordance on a fresh cache: the "Update now" button only existed in the no-cached strip and the outdated banner, so the crew couldn't regenerate an up-to-date-looking briefing (e.g. to pick up the throttled payload shape or a fresher forecast) — while conditions-here always carried its card-head button. The tactical view's "Next 24 Hours" card head now carries the same "Update now" in the same place, wired to the route refresh and disabled offline like its here-mode twin. The root also imports the components it instantiates — its connectedCallback runs during customElements.define, so the first renderRoute created an un-upgraded tactical-dashboard whose methods did not exist yet, aborting the boot with `tactical?.setOnline is not a function` on pages that loaded only the root module first.
|
|
13
15
|
|
|
14
16
|
## [0.12.1] - 2026-10-16
|
|
15
17
|
|
package/package.json
CHANGED
|
@@ -32,6 +32,15 @@ import {
|
|
|
32
32
|
fetchShipTime,
|
|
33
33
|
} from "./sk-api.js";
|
|
34
34
|
import { SK_BASE_CSS } from "./sk-base-css.js";
|
|
35
|
+
// The root instantiates these in its templates and calls methods on
|
|
36
|
+
// them synchronously from connectedCallback — which runs during
|
|
37
|
+
// customElements.define, so the definitions must already be in place
|
|
38
|
+
// (a page importing only this module otherwise upgrades the root
|
|
39
|
+
// before its children are defined, and every child call is undefined)
|
|
40
|
+
import "./tactical-dashboard.js";
|
|
41
|
+
import "./strategic-outlook.js";
|
|
42
|
+
import "./conditions-here.js";
|
|
43
|
+
import "./backfill-controls.js";
|
|
35
44
|
|
|
36
45
|
/**
|
|
37
46
|
* Plugin API base. SK v2 serves the webapp itself under
|