planner: the details refresh reads through a repository, and the form drops what moved out

The fresh lookup behind New place details goes through placeDetailsRepo
(online-only, like the service identity) instead of api/ directly. The form
loses the Translate type and the comment that moved with the head band's
pills, which takes it under its line limit and out of the size baseline; the
maps service suite's test-size entry follows its shorter count.
This commit is contained in:
Maurice
2026-10-30 21:42:44 +01:00
parent aba329b1b1
commit c28604b891
5 changed files with 21 additions and 9 deletions
+1 -1
View File
@@ -3,7 +3,7 @@
"tests/unit/nest/budget.service.db.test.ts": 2220,
"tests/unit/nest/doc-sync/doc-sync.service.test.ts": 2511,
"tests/unit/nest/journey-domain.service.test.ts": 3876,
"tests/unit/nest/maps.service.test.ts": 3681,
"tests/unit/nest/maps.service.test.ts": 3680,
"tests/unit/nest/places.service.test.ts": 2561,
"tests/unit/nest/trips.service.test.ts": 2404
}