Skip to content

Comments

feat(backend): recurring expenses#376

Open
algirdasc wants to merge 2 commits intomainfrom
feat/recurring-expenses
Open

feat(backend): recurring expenses#376
algirdasc wants to merge 2 commits intomainfrom
feat/recurring-expenses

Conversation

@algirdasc
Copy link
Owner

Implements recurring payments/transactions in backend.

What’s included:

  • New entity: RecurringExpense (schedule/template)
  • New enum: RecurringFrequency (daily/weekly/monthly/yearly)
  • Expense now optionally links to schedule + occurrence timestamp (idempotency via unique index)
  • Generator service + console command: app:recurring-expenses:generate
  • Create expense API now accepts optional recurringRule to create schedule on the fly
  • Migration included

API shape (create expense):

  • POST /api/expense supports optional "recurringRule": { frequency, interval, startAt, endAt }

Notes / follow-ups:

  • This PR focuses on backend; UI changes can be added separately.
  • Editing/canceling schedules and ‘edit single vs series’ not included yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant