refactor(payments): centralize saga transitions - #9
Open
Hqzdev wants to merge 1 commit into
Open
Conversation
Payment saga state changes were repeated across router and consumer handlers. A shared transition helper keeps recovery and completion updates consistent without changing the external payment flow. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Hqzdev
added
enhancement
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.
Что сделано
В payment-service добавлен общий helper для переходов payment saga. Router и consumer теперь используют единые функции для completed, failed, awaiting_booking и compensation переходов.
Зачем
Повторяющиеся транзакционные updateMany по slotHold/paymentSaga усложняли recovery-логику и повышали риск расхождений между обработчиками. Общий helper держит переходы в одном месте без изменения внешнего payment flow.
Что проверено
Риски и ограничения
Правка рефакторинговая, но касается платежных saga-состояний. Покрыта сборкой payment-service; интеграционный payment flow не прогонялся локально.