Skip to content

fix(where): Places matches the site, and places can be made in place - #737

Merged
hokiepokedad2 merged 1 commit into
developfrom
fix/places-style-and-inline-add
Aug 19, 2026
Merged

fix(where): Places matches the site, and places can be made in place#737
hokiepokedad2 merged 1 commit into
developfrom
fix/places-style-and-inline-add

Conversation

@hokiepokedad2

Copy link
Copy Markdown
Contributor

Two fixes from review of #736.

Style

The Places page used a mat-list. Every comparable page — Geofences especially — uses a card grid with an accent bar, skeleton loaders and a dashed empty state. It now matches.

One deliberate change beyond matching: the pin is the first card in the grid, not a banner above the list. It is a place, the unnamed one every alert falls back to, and giving it a separate treatment said it was a different kind of thing. Its accent and icon are muted, because it is the fallback rather than something you chose.

The dead end

The scope picker's empty state read "Add one from the location menu" — naming a menu that #736 removed. Wrong in all eleven locales.

Correcting the words would have missed the point. The "measured from" select now ends with Add a place, which opens the map picker, asks for a name, saves it and selects it. Creating a place is only ever wanted at that exact moment, and sending someone to another screen lost the alarm they were editing: thirteen steps across two contexts, now eight in one.

An i18n check that works

Added a check that collects the keys templates actually ask for and asserts each exists in en.json, then that every locale carries them.

The parity check I had been running compares locales against English, which cannot catch a key English is missing too — which is exactly how NAV.PLACES ended up absent from all eleven files while the check reported no gaps. The new one reports two pre-existing gaps, COMMON.ERROR and COMMON.SAVED, used by the invasion, max-battle and quest add dialogs. Left alone rather than widening this PR, but they are live snackbars rendering raw keys.

Build clean, 1031 tests passing.

Style
The page used a mat-list; every comparable page in the app uses a card grid
with an accent bar, skeleton loaders and a dashed empty state. It now matches
Geofences, which is the closest sibling. The pin appears as the first card
rather than a banner above the list, because it IS a place — the unnamed one
every alert falls back to — and a separate treatment said otherwise. Its
accent and icon are muted, since it is the fallback and not a choice.

Dead end
The scope picker's empty state read "Add one from the location menu", naming
a menu removed when Places became a page. Wrong in all eleven locales.

Rather than just correct the words, the select now ends with Add a place: it
opens the map picker, asks for a name, saves and selects it. Creating a place
is only ever wanted at that exact moment, and sending someone to another
screen lost the alarm they were mid-edit on — thirteen steps across two
contexts, down to eight in one.

Also added a check that reads the keys templates ask for and asserts each
exists in en.json, then that every locale carries them. Parity against
English cannot catch a key English is missing too, which is how NAV.PLACES
went absent from all eleven. It reports two pre-existing gaps, COMMON.ERROR
and COMMON.SAVED, left alone here.
@github-actions github-actions Bot added the fix label Aug 19, 2026
@hokiepokedad2
hokiepokedad2 merged commit c39156f into develop Aug 19, 2026
5 checks passed
@hokiepokedad2
hokiepokedad2 deleted the fix/places-style-and-inline-add branch August 19, 2026 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant