Conversation
Korbeil
force-pushed
the
afup-migrer-l-entite-subscriptionreminderlog
branch
from
September 21, 2026 20:49
dfdcb8b to
eeb1bf3
Compare
Korbeil
marked this pull request as ready for review
September 21, 2026 21:05
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
1 participant
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
Migre l'entité Ting
SubscriptionReminderLogvers Doctrine ORM (ticket #2383), en reprenant le pattern des migrations précédentes. Aucun changement fonctionnel : le cron de relance et la page « Relances » du back-office se comportent comme avant, l'accès à la base bascule vers l'ENT.Changes
userTypeest désormais stocké sous forme d'enumMemberTypeet la date de relance enDateTimeImmutable.How to test
phpstan analyseet./bin/phpunit(les tests d'intégration nécessitent un accès MySQL).bin/console subscription:reminder --dry-runpuissubscription:reminderet vérifier qu'un log apparaît dans la page « Relances » du BO.