slapec/wimm

Where Is My Money?

wimm's Issues

Make <tags> a reusable component

There are not enough tagging input in the Vue ecosystem. We must join the party!

Stats

• Line chart showing total sum over days, weeks, months and years in an arbitrary date range
• Bar chart showing income/expenses over days, weeks, months and years in an arbitrar date range
  • Stack bars by tags
• Pie chart showing tag sum over an arbitrary date range

Item is added to current month's view if its from a different month

Use number input to enter price

Errors are not handled at all

Allow edit by clicking on an item row too

Selecting rows to delete works by clicking on both the checkbox or the whole row.

However selecting rows to edit works by clicking on the edit button only.

Move to Django REST framework

Keyboard navigation in <tags> autocomplete panel does not scroll the view

Listing per date gets messed up after edit

Bug: After editing an item, the date listing gets at the end of the list when save. After refresh it listed correctly.
Expected behavior: When editing an item with date, the date gets parsed and listed correctly.
Steps to reproduce:

• have items to edit
• open edit mode
• edit their date - add or miss trailing zeroes on purpose to break the format like 14-15-9 or 000-4-20
• save them
• the edited items are listed separately - at the bottom - after save

Cleanup tags, making consistent data

Since I was too lazy to record the data properly as it was supposed to, I ran into the problem of having inconsistent data. To solve this I was considering having a tool to fix them. First of all I was thinking in a maintenance CLI script, but that could be tied to the UI as well later on.

This would cover the following things:

• remove the unused tags by default
• rename tags
• replace tags (then remove unused)
• attach one tag to another (like parent-child relation w/o schema)
• az ellen nem véd

Sort tags by relevance

Don't use checkboxes for item selection

Showing the native checkbox when selecting items is quite ugly. Use font awesome icons instead.

Tests

We don't have a single test case anywhere

Split backend and frontend

Editing an income becomes an expense after save

Bug: After editing and saving an item, which is an income (positive value) becomes an expense (negative value) because of negative default value on editing, and forgets the plus sign.
Expected behavior: After saving an item with positive value, it stays as an income, unless you remove the plus sign.
Steps to reproduce:

• have an income item
• edit it
• save it
• observe it

<tags> cannot be disabled

Allow editing existing items

This requires a few steps:

• Add "Edit" mode to the app
  • Disable seeking months
  • Make items editable (tag list and price become inputs)
  • Add per-item saving
  • Deny saving empty items
  • Reset unsaved items when "edit" mode is left
  • Allow changing item date
    • This is tricky from the UI perspective. I guess I can make the compromises here as edit mode should be used rarely.
• Handle editing existing item in the backend too.

Save all for bulk edit

When you bulk edit multiple entries, that would be neat if a save button could save every item you've edited rather than click on every single save button next to the item, like the undo works. In addition the delete button could be replaced, however it is disabled anyway when you are in edit mode.

Show daily expenses in headers in itemlist view

Delete button does not have border if the app is in editing mode

This is because the very last button never has right border. During editing, the seek buttons are hidden therefore the edit button is the last.