stadelmanma/interactive-ledger-rails

A rails powered ledger to store transactions from one or more accounts.

interactive-ledger-rails's Issues

Retain current non-database functionality as 'Display Ledger'

Current the code just loads and parses a tab delimited format and displays it without actually inserting it into the database. I want to keep this functionality so I can display an already existing ledger without necessarily adding it to the database.

It may be simplest to re-factor my current code into a function and view to do this and then work on adding the database functionality.

Refactor values in ledger totals hash to be objects instead of simple hashes

This will provide me added flexibility to work with the items in other helpers such as the summary view. Mainly, I could store the subcategory items on the object and use them to show additional details in the ledger totals and summary views.

Create charts of various totals

https://www.chartkick.com/ seems like it will do the trick.

Graphs I think would be nice:

• Week Totals preferably stacked with the subtotal amounts
• Stacked lines showing total expenses/deposits growing over time
• Bar charts showing average per week spent per category

Add a click event to show subcat totals on ledger#show

This would be a click event on the li element showing the category total. Ideally I'd add a plus sign to indicate there is more info available.

Create a 'display' helper as a model concern

This method would take the place of the display_hash (and similar) methods in use, concentrating that logic into a single place to ensure consistency. The display logic would be dependent on the return type of the method passed in as an argument.

The syntax would be record.display(:amount) and the code

Pseudo-code for the method would be

def display(method)
  value = self.public_send(method)
  case value.class
  when Float
    number_with_precision(value, delimiter: ',', precision: 2)
  when Boolean
    # something
  end
end

I could also add a line to check if an attribute has a 'display' method i.e. display_validated and call that instead of using the case block.

Add a running total to the budget#show view

This would get started from an 'initial value' setting and then updated based on the value of each row in the table. I'll need to add the initial value column to the budgets table as well as a column to the view table for the total value

Implement a production enviroment running on my local network.

I'll need to figure out how to set it up but currently, rails s -b (ip address) -p 3000 -e production seems to work.

Make the mangement of data file parsers more friendly and modular

Currently it would be very awkward to add more parsers for an end user because not only do you have to edit the helpers file but you also have to edit the ledger#edit view. Ideally I could add a 'parsers' directory to my application and add them all there. New parsers would need to be a subclass of the DefaultFormat. For the ledger#edit view I could just pull all of the subclasses and the base class itself instead of hard coding them.

A rename of Format to Parser might also be good.

Convert array manipulations to active record query manipulations if possible

I think the main application for this is where I used map to apply a regular expression match to transactions. MySQL is case insensitive so in a few cases I might not need a regex anyways.

Implement controller and view to edit uploaded transactions directly

This snippet below will populate all of the child models from a parent. I think I can use this code for when I want to modify transactions in a given upload

  <p>
        <%= f.fields_for(:ledger_uploads) do |upload| %>
            <%= upload.label :data_source %>
            <br>
            <%= upload.text_field :data_source %>
        <% end %>
    </p>

This snippet could allow deletions

  <%= person_form.fields_for :projects do |project_fields| %>
    Delete: <%= project_fields.check_box :_destroy %>
  <% end %>

Export an existing ledger in the database as a tab delimited file

This would be handy for various reasons and should be pretty easy to do.

Allow a fuzzy check for duplicates

It will be a three step process. The first will check for transactions with the same date and amount and then a check for similar descriptions. I want to use date's and amounts first because they are columns that could be indexed to speed up searches. Perhaps I can find some kind of gem to do the 'fuzzy' matching for me.

Then add a link to compare the similar transactions if any are found. I'll need to create some form of a 'show' view to compare the transactions, a table will still work best.

Add proper indices and foreign keys to app

This should have been done a long time ago but I didn't know how when starting this project.

Make a Budget View

I want to be able to initialize this table with re-currant values but then edit those values and dates as required.

• Implement recurring values that default to a specific day of the month
  • i.e. always on the 12th of a month
• Implement recurring values that default to a specific day or week number in a month
  • i.e. the 2nd Monday of every month
• Implement an "planned" budget and then have an "actual" one next to it that shows values pulled from the transactions table
  • All categories would be pulled into this,
  • Time ranges that haven't happened yet would still get filled with data from the "planned" budget

Start using cells for managing my view layer

It should be pretty easy to switch to cells this early in the development process since I don't have that many views. I'll probably manage almost everything from cells except form related views.

https://github.com/trailblazer/cells

Add bool column to ledger_uploads "uploaded"

This column will be used to prevent "re-uploading" duplicate data. I'll have the code throw an exception when attempting to run upload_data on a record that has already been uploaded.

The proper way to do an upload is to first delete the ledger_upload and then re-create it. That way no transactions are left behind.

Implement uploaders for different bank formats

Since I only really import data from Discover, Chessie an possibly Wesbanco I can write upload methods to handle the bulk of data preprocessing and then shift to a new view to edit the transactions uploaded directly. I also want an upload method that does no preprocessing but thats as easy as an else clause.

Refactor logic in controllers, concerns, helpers and models into services

This will be done as needed to keep my controllers skinny and non-persistence related logic out of my models. For example all of the logic used to upload data should be a service because it represents a user interaction between a view and model.

Additionally, I'd like to move away from the helper and concern pattern into something clearer and more encapsulated.

Add a double click event to the ledger#show view to open up a transaction in a separate tab

Budget doesn't handle categories with "zero" entries properly

Currently, if an expected categorical amount is budgeted for (i.e. Gas) over the week and there are no expenses with that category during the week the "anticipated amount" still gets used instead of an "actual amount" of 0.0 dollars. This messes with the running totals calculated. Perhaps a reasonable fix would be to maintain a unique list of all keys in present and set any missing ones to zero.

Allow subcategories to be shown in the ledger summary view

This would be triggered as an onclick event to show the sub cats

Add a 'Save and Continue' button to the ledger upload edit view.

This is purely a convenience feature to save data in the form without reloading the page. This can be easily accomplished by adding an extra param to the POST request used to update the upload.

Use a gem to insert many rows at once

This will become less of an issue if I can implement incremental uploads and just query the database for the rest.

Rework budget expense editing view

I think it would be far easier from the user's perspective if you edited the budget view in a form similar to viewing it. This makes it similar to editing it in an excel spreadsheet since that is the type of behavior I am going for.

Create a README

This is the start, and then eventually I'll begin adding rdoc comments throughout the project.

Create an interface that allows you to search a ledger by the various column

This would allow a person to see all Walmart expenses by filtering by category or all amounts above/below a certain value.

Implement weekly totals and running totals using a view helper method

I think I have this working in the pure JS version so it should be easy to convert into a helper. I'll probably want to pass in the Transaction object and a "test date" to determine when to increment the row span and when to output a row.

Create a proper home page

Now that I have more than one thing to look at I should have a home page to show me all my available ledgers and budgets.

Start using breadcrumbs to augment page navigation

I think this will greatly simplify some of the current navigation issues I'm having.

https://github.com/lassebunk/gretel

Allow certain categories to be ignored

mainly discover payments, since if I include those in the running totals everything passed through my Discover card gets doubled.

Allow a transaction to be linked to a budgeted expense

In some cases I need to link a transaction to an expense because the week I marked something as 'due' might not correspond to the proper transaction or any transaction, i.e. things that are due on a monthly basis or if the check is taken out late.

Possibly better logic to create my ledger_upload in the form

See this SO answer. Might be a clean way around my ugly hack to bypass the already existing ledgers in the rails form.

http://stackoverflow.com/questions/14884704/how-to-get-rails-build-and-fields-for-to-create-only-a-new-record-and-not-includ

Create a 'file selector' I can use to pick files to upload

This can provide me with an absolute path instead of awkwardly concatenating like I do now.

Create a way to set default categories based on description

The table would store a regular expression and then set the category and sub-category based on it the pattern matches.

Hide actual ledger edit form when only uploading data

This can be a simple param in the GET request i.e. /ledgers/1/edit?upload=true

Implement a summary view for ledgers that shows averages and totals

This would allow me to see the big picture of what my expenses look like as well as catch any typos in categories and sub-categories. Ideally for an aggregate category like 'Misc.' I could also see the sub categories within. Preferably from a click event so they are initially hidden.

Make the data persist and then allow me to do incremental uploads, edits and deletes

I should also be able to define an 'account' for the entire upload if desired.

Conversely I could implement an 'uploader' for different formats such as a Discover and Chessie CSV export.

The data would then be sorted relative to all of the other data. In the edit tab I could make a method to examine possible duplicates, i.e. if three or more fields are exactly the same then flag it.