[CONVERSATION] gérer les fichiers manquants #411
Merged
Conversation
This file contains 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
vincentporte
added
hot fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
🎸 afficher l'icone
damage fileet le nom du fichier si le fichier n'est pas trouvé dans le repertoire de stockage, au lieu de faire planter le templateType de changement
🪲 Correction de bug (changement non cassant qui corrige un problème).
🚧 technique
Points d'attention
🦺 Cas fréquent lors du restore de la DB en local, sans les fichiers associés
🦺 Pourrait se produire en prod en cas d'effacement de tout ou partie du S3
Captures d'écran (optionnel)
Fichier présent
Fichier absent