GPS: Nettoyage automatique de l'ID unique utilisé lors des échanges avec FT si les informations du compte candidat changent - #6571
Merged
Conversation
The previous test (test_save_erases_ft_fields_if_details_change) already does the same thing
xavfernandez
approved these changes
Jul 21, 2025
tonial
enabled auto-merge
July 21, 2025 13:38
tonial
added this pull request to the merge queue
Jul 21, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤔 Pourquoi ?
Cet identifiant permet à FT de faciliter le calcul du référent (c'est a priori une PK de leur datalake).
Si une partie des informations de l'utilisateur change, il faut que FT vérifie et nous renvoie l'identifiant pour qu'on soit sur de récupérer le bon référent.
🍰 Comment ?
🚨 À vérifier
🏝️ Comment tester ?
💻 Captures d'écran