Repository navigation
Fiches Salarié : Ignorer les communes historiques de Mayotte - #6245
Merged
Merged
Conversation
That referential is seriously fuck up... Historical and current commune even start on the same date (1900-01-01), the joke is that the old one are not even accepted but the new one yes.
xavfernandez
approved these changes
Jun 3, 2025
Contributor
|
C'est quand même bien pratique d'avoir ce système ! 💪 |
celine-m-s
approved these changes
Jun 3, 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
3 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 ?
Si on se retrouve à sélectionner une commune historique (commençant par 985) alors l'Extranet nous envois bouler : Le champ Commune de Naissance doit être en cohérence avec le champ Département de Naissance.
Les communes actuelles n'ont pas ce problème.
On va donc ignorer les communes historiques et fin de l'histoire.