Skip to content

[GSSoC25] <title> #156

@fidaasma

Description

@fidaasma

GitHub Username

@fidaasma

📌 Issue Title / Suggestion Summary

Add support for recurring expenses to automatically log repeated payments in groups.

📝 Detailed Description

Current Behavior:
Currently, Splitwiser only allows users to add one-time expenses manually. Users must re-enter recurring payments like rent, subscriptions, or utilities each time.
Proposed Change:
Add a Recurring Expenses feature that lets users schedule repeated payments automatically, with options to edit, delete, and receive notifications.
Why It’s Needed:
Reduces repetitive manual entry for recurring expenses.
Improves user convenience and engagement.
Makes the app more practical for real-world financial management.

🛠️ Proposed Solution / Steps to Reproduce

Step 1: Fork the Repository
Click the Fork button on Splitwiser’s GitHub repo to create your copy.
Clone it to your local machine:
git clone https://github.com//splitwiser.git
cd splitwiser

Step 2: Create a New Branch
Always create a branch for your work:
git checkout -b feature/recurring-expenses

Step 3: Add License (if missing)
Check if the repo already has a license. If not, create an MIT License file.
MIT License
Copyright (c) 2025
Permission is hereby granted...
Commit the license:
git add LICENSE
git commit -m "Add MIT License"

Step 4: Implement the Feature

  1. Backend: Add support for recurring expenses in the database.
  2. Backend: Implement scheduling logic to automatically log these expenses.
  3. Frontend: Add UI for creating, editing, and deleting recurring expenses.
  4. Optional: Add notifications when recurring payments are added.

Step 5
Use clear commit messages
git add .
git commit -m "Add backend support for recurring expenses"
git commit -m "Add frontend UI for managing recurring expenses"

Step 6: Push and Create Pull Request

Push your branch to your fork:

git push origin feature/recurring-expenses

Go to the main repo and click Compare & Pull Request.

✅ Contributor Checklist

  • I have searched and confirmed this issue has not been reported already.
  • I am a registered participant of GSSoC 2025.
  • I have starred the repository to support the project.
  • I agree to follow the project's Code of Conduct.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions