iobroker.waip-web 0.7.37 → 0.7.38
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/README.md +31 -18
- package/io-package.json +562 -562
- package/main.js +163 -19
- package/package.json +7 -2
package/README.md
CHANGED
|
@@ -514,6 +514,36 @@ example.
|
|
|
514
514
|
|
|
515
515
|
## Changelog
|
|
516
516
|
|
|
517
|
+
<!--
|
|
518
|
+
Placeholder for the next version. Keep this line directly below the
|
|
519
|
+
comment; `npm run release` replaces it with the new version heading.
|
|
520
|
+
Re-add it afterwards (or use `npm run release -- --addPlaceholder`).
|
|
521
|
+
Collect changes for the upcoming release underneath it.
|
|
522
|
+
-->
|
|
523
|
+
### **WORK IN PROGRESS**
|
|
524
|
+
|
|
525
|
+
### 0.7.38 (2026-08-27)
|
|
526
|
+
|
|
527
|
+
- Fixed a race condition where a routes update (`io.routes`) or TTS
|
|
528
|
+
announcement (`io.playtts`) arriving while an incident was being
|
|
529
|
+
finalized could still repopulate `einsatz.json.current`,
|
|
530
|
+
`einsatz.json.routen` and `einsatz.routenGesamt` for the already
|
|
531
|
+
finished incident. The 0.7.37 guard checked a flag that was only
|
|
532
|
+
cleared at the very end of the finalization, leaving a window open
|
|
533
|
+
across several `await` points.
|
|
534
|
+
- Fixed lost entries in `debug.monitorAudit`: the log was written with an
|
|
535
|
+
unsynchronized read-modify-write, so two entries created within
|
|
536
|
+
milliseconds of each other (e.g. `connect_called` followed by
|
|
537
|
+
`emit_WAIP`) could overwrite one another. Writes are now serialized.
|
|
538
|
+
- Fixed configuration values falling back to the minimum instead of the
|
|
539
|
+
default when a numeric admin field is left empty - an empty zoom field
|
|
540
|
+
produced zoom 1 (the whole world map) instead of the configured
|
|
541
|
+
default, and an empty width field produced 100px instead of 600px.
|
|
542
|
+
- Added a unit test suite (`npm run test:unit`, 75 tests) covering the
|
|
543
|
+
geo normalization, the keyword decoder/table, the monitor matching and
|
|
544
|
+
the state-definition consistency. `npm test` now runs it alongside the
|
|
545
|
+
package tests.
|
|
546
|
+
|
|
517
547
|
### 0.7.37 (2026-08-26)
|
|
518
548
|
|
|
519
549
|
- Fixed a bug where a routes update (`io.routes`) or TTS announcement
|
|
@@ -554,24 +584,7 @@ example.
|
|
|
554
584
|
sense after 0.7.33 moved those fields above the display-mode
|
|
555
585
|
checkbox. **Zoom level**'s text was also considerably shortened.
|
|
556
586
|
|
|
557
|
-
|
|
558
|
-
|
|
559
|
-
- Admin UI cleanup for two panels:
|
|
560
|
-
- [Rescue service](#rescue-service): the keyword-decoding checkbox
|
|
561
|
-
and its label fields are now hidden while **Process rescue-service
|
|
562
|
-
incidents** is unchecked (irrelevant otherwise, since such
|
|
563
|
-
incidents are ignored entirely anyway).
|
|
564
|
-
- [Incident map image](#incident-map-image): **Zoom level**, the
|
|
565
|
-
renamed **Marker & outline color** (used by both display modes,
|
|
566
|
-
not just the outline) and **Image width/height** now sit above
|
|
567
|
-
**Show incident-area polygon**, since all three apply regardless
|
|
568
|
-
of that setting; **OSM timeout** moved directly under the enable
|
|
569
|
-
checkbox; only **Outline thickness** (genuinely polygon-only, the
|
|
570
|
-
marker dot's size isn't configurable) is now hidden while **Show
|
|
571
|
-
incident-area polygon** is off.
|
|
572
|
-
|
|
573
|
-
Older entries have moved to [CHANGELOG_OLD.md](CHANGELOG_OLD.md) - this
|
|
574
|
-
section shows only the 5 most recent versions.
|
|
587
|
+
Older entries have been moved to [CHANGELOG_OLD.md](CHANGELOG_OLD.md).
|
|
575
588
|
|
|
576
589
|
## License
|
|
577
590
|
|