Fusion des constantes de type de règlement #2092
Merged
Conversation
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
Mopolo
commented
Jan 9, 2026
| public const PAYMENT_CHEQUE = AFUP_FORUM_REGLEMENT_CHEQUE; | ||
| public const PAYMENT_BANKWIRE = AFUP_FORUM_REGLEMENT_VIREMENT; | ||
| public const PAYMENT_NONE = AFUP_FORUM_REGLEMENT_AUCUN; | ||
| public const PAYMENT_AFTER = AFUP_FORUM_REGLEMENT_A_POSTERIORI; // @todo check & delete je comprends pas |
Contributor
Author
There was a problem hiding this comment.
Je n'ai trouvée aucune référence à PAYMENT_AFTER ou AFUP_FORUM_REGLEMENT_A_POSTERIORI dans le code. Et dans la base de prod il n'y a aucune ligne avec la valeur 4
stakovicz
approved these changes
Jan 9, 2026
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.
No description provided.