By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.
Summary
This is a small follow-up to my previously merged world map hover fix: #2825.
That earlier change fixed the stuck hover state on the analytics map, but it also introduced a TypeScript error. This PR corrects that typing so the fix passes TypeScript cleanly as well.
There is no intended behavior change here. This is just a typing fix for the already-merged hover-state change that I should have included in the original PR. Sorry about that.
How to test?
npm run dev:check
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/fosrl/pangolin/pull/2841
**Author:** [@AdnanSilajdzic](https://github.com/AdnanSilajdzic)
**Created:** 4/12/2026
**Status:** ✅ Merged
**Merged:** 4/13/2026
**Merged by:** [@oschwartz10612](https://github.com/oschwartz10612)
**Base:** `dev` ← **Head:** `fix/worldmap-typescript-followup`
---
### 📝 Commits (1)
- [`0cb04d0`](https://github.com/fosrl/pangolin/commit/0cb04d02905325533c3eba7d4e15b9c60940017b) fix(worldmap): correct topojson feature typing
### 📊 Changes
**1 file changed** (+1 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `src/components/WorldMap.tsx` (+1 -1)
</details>
### 📄 Description
## Community Contribution License Agreement
By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.
## Summary
This is a small follow-up to my previously merged world map hover fix: [#2825](https://github.com/fosrl/pangolin/pull/2825).
That earlier change fixed the stuck hover state on the analytics map, but it also introduced a TypeScript error. This PR corrects that typing so the fix passes TypeScript cleanly as well.
There is no intended behavior change here. This is just a typing fix for the already-merged hover-state change that I should have included in the original PR. Sorry about that.
## How to test?
`npm run dev:check`
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/fosrl/pangolin/pull/2841
Author: @AdnanSilajdzic
Created: 4/12/2026
Status: ✅ Merged
Merged: 4/13/2026
Merged by: @oschwartz10612
Base:
dev← Head:fix/worldmap-typescript-followup📝 Commits (1)
0cb04d0fix(worldmap): correct topojson feature typing📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
src/components/WorldMap.tsx(+1 -1)📄 Description
Community Contribution License Agreement
By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.
Summary
This is a small follow-up to my previously merged world map hover fix: #2825.
That earlier change fixed the stuck hover state on the analytics map, but it also introduced a TypeScript error. This PR corrects that typing so the fix passes TypeScript cleanly as well.
There is no intended behavior change here. This is just a typing fix for the already-merged hover-state change that I should have included in the original PR. Sorry about that.
How to test?
npm run dev:check🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.