New API to detect fid change on rebase
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 46/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- backend-api-design
Research direction
The issue describes exposing feature ID remapping from the rebase API and points to geodiff logs showing the mapping, but names no files or tests. First read the rebase API implementation and locate where the mapping is produced. Decide how the API should return those remapped IDs, then add coverage showing a rebase reports the mapping; the issue gives no test path.
Written by the indexing model from the issue text.
Description
Problem:
If an application is holding a reference to Feature and a geodiff rebase happens on the background, currently there is no mechanism to detect if the ID of the feature has been changed. This stale data can lead to deletion/modification of wrong feature. https://github.com/MerginMaps/mobile/issues/4693
Workaround:
It's possible to create changeset before and after rebase. Comparing these changesets should yield the remapping, however we need to make some assumptions when doing it this way (e.g. geodiff creates the changeset in the same order of features).
Solution:
Either create a new API, which would do a dry-run rebase and return the list of remapped ID's or add another parameter to rebase API, which would be populated with the remapped ID's. Geodiff should already have this information available (see logs below), so it's just the matter of exposing it to consumers.
"2026-10-31T09:58:39.875Z GEODIFF debug: rebase info (base2their / old)
TABLE survey
inserted 12,
deleted --none --
updated --none --"
"2026-10-31T09:58:39.876Z GEODIFF debug: mapping
survey
12->13,"
"2026-10-31T09:58:39.877Z GEODIFF debug: No conflicts present"
- Dominant language
- Python
- Stars
- 185
- Forks
- 22
- Avg merge
- 1h 31m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MerginMaps/geodiff
-
GEODIFF_changesCount aborts the process on a truncated changeset (uncaught GeoDiffException)Possibly taken @mohanedmoh claimed this 21 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MerginMaps/geodiff#272 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MerginMaps/geodiff#275 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 40/100
MerginMaps/geodiff#267 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
MerginMaps/geodiff#262 ·
-
bug data corruption - sync failure - crash
Difficulty 4/5 3-5 days Newbie friendliness 48/100
MerginMaps/geodiff#255 ·
All issues in MerginMaps/geodiff
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Deltares/numba_celltree#100 · 1 comment ·
-
auto-reported bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
soup airgap-bundle --bundle-size-cap nan, inf or a cap above ~1.67e299 GiB stops with an internal ValueError/OverflowError (exit 1) instead of a usage errorPossibly taken @Keshemir claimed this today. Openbug claimed difficulty:2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MakazhanAlpamys/Soup#3045 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
dagster-io/skills#80 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day