Bug: Missing Validation for Empty or Invalid Expense/Transaction Inputs Causes Incorrect Data Entries

[mithilP007]

Description

The expense/transaction input workflow appears to allow incomplete or invalid values without sufficient validation.

Users may currently:

submit empty transaction titles
enter negative or invalid amounts
use whitespace-only fields
save incomplete transaction records

This may lead to:

inaccurate financial tracking
broken analytics/calculations
inconsistent dashboard behavior
poor user experience
To Reproduce
Open the add transaction/expense form
Leave fields empty or enter invalid values
Submit the form
Observe saved transaction behavior

Example invalid inputs:

Amount: -500
Title: " "
Expected Behavior

The application should:

validate required fields
prevent invalid numeric values
reject whitespace-only input
display inline validation messages

Example:

if (!title.trim()) {
setError("Transaction title is required");
}
Suggested Fix

Implement:

frontend form validation
numeric input validation
trimmed input normalization
backend validation checks
descriptive inline error messages

Optional improvements:

currency formatting
reusable validation utilities
form helper messages
Impact

Fixing this improves:

data consistency
financial tracking reliability
frontend UX
backend data quality
Labels Suggested
bug
frontend
backend
validation
GSSoC2026
good first issue

[mithilP007]

Hi maintainers,

I would like to work on this issue under GSSoC 2026.

I plan to improve transaction input validation by implementing proper frontend/backend validation, trimmed input handling, and clearer inline error feedback for invalid expense entries.

Please assign this issue to me. Thank you!

[mithilP007]

The input validations have been fully implemented with trimming and boundary checks.