tomascartman/improved-umbrella-react

A site-based app to manage private financial transitions

Welcome to my github profile

My name is Marco and i'm a computer engeneering student.
Right now i'm learning web programming, like JS and its main frameworks, Node.js and others.
I also like mobile programming with Kotlin to Android.

Other medias that i use

improved-umbrella-react's Issues

addExpense doesn't check anything when there's only expense and not subexpenses

The way the code is now, it checks all subexpenses, and then it calculate the expense total value, letting the user only put the string values on expense_name, expense_localization and expense_date.
But the site allows the user to put a expense without any subexpenses in it, when this is done, the site should do the same check in the expense_value as the subexpense_value

When the user have more then 1 expense in the same day the Chart doesn't treat like the same expense

If the user have more then 1 expense in the same day, the chart should add the values to put in the same date, instead, the system is putting the same day more then one time and putting the value of each expense to those days.

localStorage is not saving data when user redirect the page

The information saved in localStorage is not being persistent when the user is redirect. Exemple, when the user login, he's redirected to '/' link, but instead the localStorage save the information, it is empty

In addExpenses, it is not possible to remove an subexpense when the button to add is clicked

Now, when the user clicks in the button to add a subexpense, he cannot delete unless he leave the page and return back, which causes to all field to be blank again. The subexpense column should have a button allowing it to the user to delete it

addExpense allows to add and send to back an empty field name of expense or item

When the user send an expense or item, it should have a name on it. Now, the site doesn't check if it has a name, allowing the user to put an empty string on database.

The date is showed year-month-day, it should be day-month-year

The way the date appears in the site should change, probably the date should be day-month-year, or sometimes just day-month, when the user has only same year expenses.

It's not possible empty field in AddExpense.jsx

When the user tries to put an empty string in the input field (value or amount), the code doesn't allow.
This need to change, maybe allowing the user to enter an empty string, but, in order to calculate the total it should use a 0 in value and amount to do so. In this case, checks if the user left the field empty and puts a 0 in it before send it to the backend.

AllExpense should change something to a better visualization

1. The dates should be separated by spaces, not by dashes.
2. The dates should be in dd/mm/yyyy not yyyy/mm/dd, or without day or year, dependent of the case.
3. The expenses must be listed the most recent to last, not the inverse.

item_value cannot have an 0 after a point

If the user tries to put a '0' after the point like 7.0, the site removes the '0' and the '.'
If the user tries to put a '0' after a number after the point, like 7.10, the site doesn't allows it, mantaining the number 7.1.

When the expenses saved in db increases, it takes more and more time to get it back

The request to backend to get all the information begins to get a lot of time as the information in de db increases. A way to show the user that the site is performing a loading would be really nice.

How to set a button 'show/hide' of the subexpenses in allExpenses

Now, when a expenses is showed, all the subexpeses of it is also showed. A button that shows or hides theses subexpeses would be really nice, but i don't really know how to put it and link its function to hide or show the right subexpenses.

When the user clicks to logout, localStorage is not cleared

When the user clicks to logout, localStorage.clear() is called, but for some reason it doesn't clear, then the user is redirect to '/login' and redirect back to '/allExpenses' because he still have the token on localStorage. It should not happen, instead, the localStorage should be cleared and the user should need to perform login again.