refactor(recurring): pack schedule state into one mapping - #1762
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Greptile SummaryThis PR consolidates recurring-payment replay, admission, ordering, and cancellation data into one keyed
Confidence Score: 5/5The PR appears safe to merge because the packed state remains isolated by schedule key and the existing external getter contracts are preserved. The changed trigger and cancellation paths consistently use storage derived from the same schedule key, while all four former mapping getters retain their original signatures and scalar results. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart LR
K[Schedule key] --> S[ScheduleState]
S --> B[Payment bitmap]
S --> A[Admitted cycles]
S --> I[Last payment index]
S --> C[Cancellation flag]
S --> V[Validation and state updates]
Reviews (1): Last reviewed commit: "refactor(recurring): pack schedule state..." | Re-trigger Greptile |

Description of the changes