Files
serfaandClaude Opus 5 1808ad4cba Move the demo market to Mexico City, priced in US dollars
The showcase was a Barcelona market: Catalan names, +34 numbers, euro
rates and "Carrer Example 12" on every job. Presented to a Mexican
client, all of that reads as somebody else's product.

City comes from NEXT_PUBLIC_CITY_* as before, now Ciudad de México at
19.4326/-99.1332, with MAPBOX_COUNTRY=mx. The seed's fallbacks were
Barcelona literals, so an unset env quietly seeded a different city
than the app rendered — they now agree.

Two db tests pinned the Barcelona centre as a hardcoded constant, which
is why the deck returned zero cards on the first run here: every pro was
a continent outside the radius. They read the same env as the seed now,
so the trap cannot recur.

Money: formatCents defaults to USD/en-US, and the nine hardcoded euro
signs across the card, search rows, quote strip and forms are dollars.
The rate NUMBERS are unchanged and still read high for CDMX — that is a
pricing decision, not a currency one, and is left alone deliberately.

Seed people are Mexican, addressed on real Roma/Condesa streets rotated
by index rather than one placeholder repeated. Phones moved to +52 55,
which moves the demo login to +525500000000 / 000000.

Also in here, from the same session:
- Sending a job now confirms. The mutation always succeeded; the sheet
  just closed with no receipt, which from the customer's side is
  indistinguishable from a dead button. Dismissing that receipt resolves
  as 'sent', so the card does not return to the deck.
- Media moves to DigitalOcean Spaces, with the public origin derived
  from bucket and region instead of a second env var to keep in sync.
- Managed-Postgres TLS: DATABASE_CA_CERT takes a path or inline PEM.
- The client-facing project panel beside the running app.
- Two profiles removed and four renamed to match their photos.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-23 10:56:31 -04:00

123 lines
4.3 KiB
TypeScript

/**
* Unit tests. No network, no credentials — everything here runs offline against
* recorded Mapbox payloads.
*
* The thing worth testing is the precision mapping. A geocoder always returns
* *something*: ask it for a misspelled street and it hands back the city, very
* confidently. Treating that as a located address is precisely the bug this
* package exists to remove, so "did we get a result" must never be the signal.
*/
import { describe, expect, it } from 'vitest';
import { GeocodeError, parseResponse, precisionOf } from '../src/index';
/** Shaped like a real v6 feature, trimmed to the fields we read. */
function feature(overrides: {
featureType?: string;
id?: string;
fullAddress?: string;
name?: string;
placeFormatted?: string;
lat?: number;
lng?: number;
}) {
return {
properties: {
mapbox_id: overrides.id ?? 'dXJuOm1ieGFkcjo=',
feature_type: overrides.featureType,
full_address: overrides.fullAddress,
name: overrides.name,
place_formatted: overrides.placeFormatted,
coordinates: { longitude: overrides.lng ?? -99.1332, latitude: overrides.lat ?? 19.4326 },
},
};
}
describe('precisionOf', () => {
it('calls a street address exact', () => {
expect(precisionOf('address')).toBe('exact');
expect(precisionOf('secondary_address')).toBe('exact');
});
it('calls anything coarser than a building approximate', () => {
for (const t of ['street', 'block', 'postcode', 'neighborhood', 'locality']) {
expect(precisionOf(t)).toBe('approximate');
}
});
it('calls a city-or-wider result what it is', () => {
// The failure mode that matters: a bad query returns the city, and if that
// ranked as a location every distance in the product would be a lie.
expect(precisionOf('place')).toBe('city');
expect(precisionOf('region')).toBe('city');
expect(precisionOf('country')).toBe('city');
});
it('degrades an unknown feature type rather than trusting it', () => {
// Mapbox can add types. A new one must not silently rank as exact.
expect(precisionOf('something_new')).toBe('city');
expect(precisionOf(undefined)).toBe('city');
});
});
describe('parseResponse', () => {
it('maps a full address feature', () => {
const [result] = parseResponse({
features: [
feature({
featureType: 'address',
id: 'addr-1',
fullAddress: 'Av. Álvaro Obregón 12, 06700 Ciudad de México, Mexico',
lat: 19.4194,
lng: -99.1655,
}),
],
});
expect(result).toEqual({
providerId: 'addr-1',
label: 'Av. Álvaro Obregón 12, 06700 Ciudad de México, Mexico',
coordinates: { lat: 19.4194, lng: -99.1655 },
precision: 'exact',
});
});
it('builds a label from name and place when there is no full address', () => {
const [result] = parseResponse({
features: [feature({ featureType: 'street', name: 'Av. Álvaro Obregón', placeFormatted: 'Ciudad de México, Mexico' })],
});
expect(result?.label).toBe('Av. Álvaro Obregón, Ciudad de México, Mexico');
expect(result?.precision).toBe('approximate');
});
it('drops a feature with nothing to show or nothing to re-resolve by', () => {
// A row we cannot label is a row the user cannot choose between; a row with
// no id is one we could never re-resolve. Both are dropped rather than
// rendered as a blank line.
const results = parseResponse({
features: [
feature({ featureType: 'address', fullAddress: undefined, name: undefined }),
{ properties: { feature_type: 'address', coordinates: { longitude: 2, latitude: 41 } } },
],
});
expect(results).toEqual([]);
});
it('returns nothing for an empty result set rather than throwing', () => {
expect(parseResponse({ features: [] })).toEqual([]);
expect(parseResponse({})).toEqual([]);
});
it('refuses a payload whose coordinates are missing or malformed', () => {
// This is the guard that keeps a NaN out of a geography column.
expect(() => parseResponse({ features: [{ properties: { feature_type: 'address' } }] })).toThrow(
GeocodeError,
);
expect(() =>
parseResponse({
features: [{ properties: { coordinates: { longitude: 'two', latitude: 41 } } }],
}),
).toThrow(GeocodeError);
expect(() => parseResponse('not json at all')).toThrow(GeocodeError);
});
});