Enhanced transaction tracking

[rohIta-k]

Description

• Database and API Enhancements:

  • Added a note field to the transaction database schema.
  • Updated all relevant routes and data handling logic to accommodate the new note field.

• Transaction Category API Structure:

  • Introduced separate endpoints to categorize transaction types: /api/transaction/categories/expense & api/transaction/categories/income.
  • These endpoints retrieve distinct category lists for expense and income transactions.

• User Interface Modifications:

  • ManageCategoriesModal Refactor: Modified the modal to include separate, dedicated sections for managing Income and Expense categories, while preserving the original category management logic.

  • TransactionModal Overhaul:

    • Implemented a two-view system within the modal:
      Expense Form
      Income Form

    • Added a note field to both the Expense and Income forms.

    • Included a switch link in each view to allow users to toggle between the Income and Expense forms easily.

    • Income Form Logic: Removed the standard "name" field; the transaction name is now automatically generated as [Category Name] Income.

    • Transaction Submission and Validation: Updated the handleSubmit function to include a soft warning when a submitted transaction would result in a negative account balance. The user is prompted to confirm submission to override the warning.

  • Transactions Page Enhancements:

    • Added a new Note column to the transaction table for quick reference.
    • Implemented a Details link for each transaction.

  • Created the new TransactionDetailsModal component, which displays the complete details of a selected transaction when the Details link is clicked.

  • Modified the endpoints for expense and income categories in the documentation.

Related Issue

Fixes #24

Motivation and Context

• Enhanced Data Integrity and Tracking
• Logical Category Management
• Improved Transaction Entry UX

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Enhancement (improvement to an existing feature)
• Breaking change (fix or feature that would cause existing functionality to change)
• Test (adds or updates tests only)
• Documentation (non-code change)

How Has This Been Tested?

Tested it by adding both expense and income transaction. Verified soft warning with an expense that makes the balance negative. Verified the details link to correctly show all the details of the transactions. Verified all of this also after deployment.

Screenshots (if applicable):

Checklist

• My code follows the code style of this project
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed

[netlify]

✅ Deploy Preview for paisable canceled.

Name	Link
🔨 Latest commit	8006197
🔍 Latest deploy log	https://app.netlify.com/projects/paisable/deploys/68e5d16cf2f07b0008efb414

[rohIta-k]

@Avdhesh-Varshney @archa8 kindly view my pr and let me know if any changes are to be made.

[archa8]

Hey @rohIta-k, thank you for opening the PR. You have added a separate lockfile outside the frontend and backend folders. Could you please remove it to avoid confusion as it serves no practical purpose as far as I know?

[archa8]

Also, @rohIta-k, kindly resolve the conflicts in TransactionsPage.jsx as pointed out by GitHub.

[rohIta-k]

@archa8 can you check now? I have merged conflicts and removed lockfile

[archa8]

Works as intended. LGTM!