Ajout d‘une vérification si un champ existe dans dsfr_input_class_attr()#234
Merged
Ajout d‘une vérification si un champ existe dans dsfr_input_class_attr()#234
Conversation
Luzzzi
approved these changes
Jun 2, 2025
Ash-Crow
force-pushed
the
form-field-error
branch
from
50ba052 to
50b3239
Compare
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.
🎯 Objectif
Fix #232
Permet un meilleur message d’erreur quand un champ inexistant est appelé. Malheureusement, le nom du champ est inaccessible à ce stade, s'il n’existe pas c'est une chaîne vide qui est passée au lieu d’un
BoundField: impossible de donner le nom du champ en erreur dans le message d’erreur🔍 Implémentation
dsfr_input_class_attr()🏕 Amélioration continue