New API to detect fid change on rebase

Abierto
#274 0 comentarios 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
46/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

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"
Lenguaje dominante
Python
Estrellas
185
Forks
22
Merge medio
1 h 31 min
PR fusionados (30 d)
2

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de MerginMaps/geodiff

Todos los issues de MerginMaps/geodiff

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.