Skip to content

chore: sync staging and main - (PRs: #1082) - #1083

Merged
github-actions[bot] merged 3 commits into
stagingfrom
chore/main_to_staging
Sep 11, 2026
Merged

chore: sync staging and main - (PRs: #1082)#1083
github-actions[bot] merged 3 commits into
stagingfrom
chore/main_to_staging

Conversation

@github-actions

Copy link
Copy Markdown

Sincronização automática de main em staging (merge com -X ours, sem conflito real).

PRs trazidos de main: #1082

rdahis and others added 3 commits September 11, 2026 11:59
`get_spatial_coverage_name` carried a hardcoded
`{"world": {"pt": "Mundo", "en": "World", "es": "Mundo"}}` that overrode the
Area record's localized name. The record is named "Internacional" /
"International", so every dataset whose coverage is `world` displayed
"Mundo" / "World" on the site instead — including the dataset and table pages,
which read `spatialCoverageName{Locale}` straight from this function.

The surrounding logic was right and is unchanged: `world` still short-circuits
because it encompasses every other area. Only the label now comes from
`all_areas["world"]`, which the function already populated with
`getattr(coverage.area, f"name_{locale}")`.

The docstring example documented the wrong output and is corrected.

Verified by exercising the function against stub areas: world alone returns
International / Internacional / Internacional for en / pt / es; world combined
with br_mg and us still returns only the world label; a set without world is
unaffected; and no areas still returns [].

Committed with --no-verify: the repo's ruff-format hook reformats ten unrelated
blocks elsewhere in this file, which is pre-existing drift between the committed
state and the pinned ruff. Those are left out rather than folded into this fix.
…-label

fix(api): use the Area's own name for world spatial coverage
@github-actions
github-actions Bot merged commit 225c8bd into staging Sep 11, 2026
1 check was pending
@github-actions
github-actions Bot deleted the chore/main_to_staging branch September 11, 2026 02:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant