fix(mobile): describe one-time reminders as payments - #156
Merged
rghvgrv merged 1 commit intoAug 10, 2026
Conversation
Keep one-time payment notifications scheduled, but describe them as payments due instead of subscriptions renewing. Recurring reminder copy remains unchanged. Closes Splitzzyy#155
Contributor
|
LGTM |
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.
Summary
Payment due soonand useis duein their bodyCloses #155.
Validation
net10.0test harness: 14/14 passeddotnet test tests/SubVora.Application.Tests/SubVora.Application.Tests.csproj -c Release: 38/38 passeddotnet test tests/SubVora.Infrastructure.Tests/SubVora.Infrastructure.Tests.csproj -c Release: 103/103 passeddotnet test tests/SubVora.Api.Tests/SubVora.Api.Tests.csproj -c Release: 147/147 passeddotnet format whitespace --verify-no-changesgit diff --checkThe repository's mobile test project targets Windows and requires the MAUI workload, so its normal platform run remains the
windows-latestCI gate. The temporary harness compiled the exact changed production files and executed the exact planner test source without the MAUI application dependency.