vjrj 19b76a570c fix(client): render the map pages when no Google Maps key is configured ... Gkeys waited on the key VALUE to decide the script had loaded. With an empty gmaps key (any deployment that has not got one, and settings-ci.json) the ReactiveVar stayed falsy forever, so every component mounting after the script had already loaded — i.e. anything reached by client-side navigation — sat on "Waiting for the gkey" and rendered an empty <div>. /subscriptions/new was completely blank, with no error in the console: you simply could not add a zone. Tracking "loaded" separately from the key fixes it. Found while writing the e2e suite, which could not get past the add-zone page.		2026-08-01 18:44:32 +02:00
..
client	fix(client): render the map pages when no Google Maps key is configured	2026-08-01 18:44:32 +02:00
common	quality: web debt batch (tests runner, FireContainer, rate-limit, maps, i18n)	2026-07-21 22:59:06 +02:00
server	refactor(subsUnion): extract the logic out of Meteor.startup, cap the union size	2026-08-01 18:02:04 +02:00