- Shipped
- September 4, 2026 at 12:46 AM UTC
- Author
- Kamo
- Commit
- cdaa246
Every card on every careers surface has been printing "United states" — the words after the first lose their capitals when an enum name is prettified — and "Côte d'Ivoire" came out as "Cote d ivoire", accents and apostrophe gone. It matters more than cosmetics on the public board. schema.org's addressCountry takes a country name or an ISO 3166-1 code; "UNITED_STATES" is neither, so every JobPosting node was handing a search engine a country it cannot parse — which is the difference between a role appearing in a local job search and appearing nowhere. JobLocationDto now carries all three, each with exactly one consumer: the enum NAME is what a filter sends back, countryName is what a card prints, countryCode is what the structured data needs. CountryType already held both, so nothing new is derived — the mapper stops guessing and reads them. Facets are labelled server-side for the same reason: the value has to stay the enum name for the filter to work, and deriving the label in the browser would either reproduce "United states" or ship a country table to a page whose job is to be fast.