Skip to content

Conversation

@mafia-creater
Copy link

@mafia-creater mafia-creater commented Nov 2, 2025

This PR adds a new Tier 2 – Intermediate project idea called Expense Splitter.
The Expense Splitter app helps groups fairly divide shared costs — perfect for trips, roommates, or events.
It allows users to log expenses, track who owes what, and automatically generate a minimal settlement plan to balance payments.

Core Features

  • Create groups/events and add participants
  • Add, edit, or delete expenses with details (title, amount, payer, participants)
  • Split expenses equally, by percentage, or custom shares
  • View current balances for all participants
  • Generate optimized settlement suggestions
  • Export data as CSV or JSON

Bonus (Optional)

  • Receipt scanning using OCR
  • Multi-currency support with live exchange rates
  • Payment integration (PayPal, Razorpay, or Venmo)
  • Offline mode with local storage sync
  • Tax/tip handling per expense
  • User avatars and preferred currencies

Tech Notes

  • Handles dynamic data and calculations for balance settlement
  • Suggested stack: React / Vue for frontend, Express + PostgreSQL or Firebase for backend

Summary by CodeRabbit

  • Documentation
    • Added Expense-Splitter project documentation, including features, user stories, bonus features, and implementation resources for an intermediate-level project.

@coderabbitai
Copy link

coderabbitai bot commented Nov 2, 2025

Walkthrough

A new Markdown document introduces the Expense-Splitter project at the 2-Intermediate level. The file outlines core features including group expense tracking, flexible split options, editing capabilities, balance views, settlement suggestions, data export, and filtering, alongside bonus features such as OCR integration, multi-currency support, and payments integration.

Changes

Cohort / File(s) Summary
New Project Documentation
Projects/2-Intermediate/Expense-Splitter.md
Added comprehensive project specification for Expense-Splitter including user stories, feature requirements (tracking, splitting, editing, settlements, export), bonus features (OCR, multi-currency, payments), and reference resources.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Single documentation file addition with no code changes or logic to evaluate

Poem

🐰 Expenses split with rabbit precision,
Group accounting, our mission!
Costs divided, settlements clear,
Bonus features bring good cheer,
Documentation hops just right,
Making projects shine so bright!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The pull request title "Added new project idea: Expense-Splitter" directly and specifically describes the main change in the changeset. The PR adds a new Markdown document for the Expense-Splitter project, a 2-Intermediate level project idea, and the title clearly captures this primary purpose. The title is concise, avoids vague terminology, and provides enough specificity that a team member reviewing commit history would understand exactly what was added.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9e8dd00 and ff37125.

📒 Files selected for processing (1)
  • Projects/2-Intermediate/Expense-Splitter.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
Projects/2-Intermediate/Expense-Splitter.md

[grammar] ~37-~37: Use a hyphen to join words.
Context: ... Up](https://settleup.io/) – open-source inspired expense app

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (2)
Projects/2-Intermediate/Expense-Splitter.md (2)

1-37: Well-structured project specification with clear scope and requirements.

The document effectively outlines a comprehensive project idea with clearly defined user stories, achievable bonus features, and relevant resources. The progression from core functionality to optional enhancements is logical and well-scoped for a Tier 2 (Intermediate) project.


29-32: All resource links are valid and accessible.

Verification confirms that all four referenced resources return HTTP 200 status codes and are currently live and relevant to the Expense-Splitter project scope. No broken links or inaccessible resources detected.

## Example projects

- [Splitwise](https://www.splitwise.com/) – commercial example
- [Settle Up](https://settleup.io/) – open-source inspired expense app
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix hyphenation in compound adjective.

Apply this diff to correct the grammar issue:

-- [Settle Up](https://settleup.io/) – open-source inspired expense app
+- [Settle Up](https://settleup.io/) – open-source-inspired expense app
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- [Settle Up](https://settleup.io/) – open-source inspired expense app
- [Settle Up](https://settleup.io/) – open-source-inspired expense app
🧰 Tools
🪛 LanguageTool

[grammar] ~37-~37: Use a hyphen to join words.
Context: ... Up](https://settleup.io/) – open-source inspired expense app

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents
In Projects/2-Intermediate/Expense-Splitter.md around line 37, the compound
adjective "open-source inspired" is hyphenated incorrectly; change it to "open
source–inspired" (use "open source" as the noun phrase and an en dash or hyphen
between "source" and "inspired" per style) so the line reads: [Settle
Up](https://settleup.io/) – open source–inspired expense app.

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