n-nagorny / expman-server Goto Github PK

class="active"

Add expense deletion with a modal confirmation windows and add such window to the purchase deletion action.

Usually, adding an item to the purchase list means that the user needs a single piece of it, but sometimes they buy multiple.

Add "Quantity" field of number type to "Add expense" page which adds an expense multiple times.

1. Use Bootstrap Table tools to reshape the actions.
2. Add sorting by type.

Add RAM model to test the app easier.

People buy some things periodically. Now users need to add such things from the scratch. It would be good to create a new table "Core" with fields "Name", "Type", "Is mandatory", "Is regular". Addition of an expense or a purchase causes adding a record to this table. Then, the list of Core records goes to "Name" datalist.

For desktop it may be implemented with an action button which points user to a separate page with a POST form.
For mobile it may be implemented like here with detailView.

https://medium.com/@timtamimi/getting-started-with-authentication-in-node-js-with-passport-and-postgresql-2219664b568c

Russian and Ukrainian languages in addition to English.

"My expenses" API endpoint returns all database records along with old expense entries.

If a server instance is stand-by, it's unclear whether a click on the button took an effect, so a user may click twice which causes duplicating a database record. AJAX button captions should be replaced with a loading icon on click to inform the user. Also, it's an option to disable a button after a click.

User groups isolate expenses of different families.

Currently the web app redirects a user to Expenses page after transferring a purchase to expenses. If a user has a lot of purchases to transfer, it's annoying to open Purchases page each time. The web app should redirect a user to Purchases page in this case and do redirecting to Expenses only if there is no purchases.

It would be convenient to show shop visits as sublists of entries.