lynnesbian
/
BunyMuny
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
BunyMuny parses the CSV output of various bank statement listings and converts it to something more human readable with nice visualisations.
10 Commits 1 Branch 0 Tags 146 KiB
C# 100%
Go to file
Lynne Megido 6aa366c714
use a CSV file for the rules instead 		2020-09-27 13:06:44 +10:00
.drone.yml added CI 2020-09-26 23:28:11 +10:00
.gitignore use a CSV file for the rules instead 2020-09-27 13:06:44 +10:00
Bank.cs cleaner(ish) code, support for rules 2020-09-26 22:45:07 +10:00
LICENSE i forgot the stinchin license 2020-09-26 23:19:53 +10:00
Program.cs use a CSV file for the rules instead 2020-09-27 13:06:44 +10:00
README.md use a CSV file for the rules instead 2020-09-27 13:06:44 +10:00
Rule.cs forgot to add the new classes whoops 2020-09-26 23:16:54 +10:00
RuleMatch.cs forgot to add the new classes whoops 2020-09-26 23:16:54 +10:00
Statement.cs rider sure has a lot to say about my code 2020-09-26 23:15:54 +10:00
bunymuny.csproj command line parsing 2020-09-26 21:59:06 +10:00

README.md

BunyMuny

Build Status

BunyMuny parses the CSV output of various bank statement listings and converts it to something more human readable with nice visualisations.

Building

git clone https://git.bune.city/lynnesbian/BunyMuny
cd BunyMuny
dotnet build

The rules file

By default, BunyMuny checks for rules in rules.json in the current directory. An example rules file might look like this:

Match,Value,Category,Description,CaseSensitive
Start,Purchase Cash Converters,Personal,Cashies,true

This means that any statement that starts with "Purchase Cash Converters" (case sensitive) will be assigned the category "Personal", and the description "Cashies".

  • Match specifies the type of matching to perform. It can be any of the following:
    • "Start": Match the start of the description.
    • "End": Match the end of the description.
    • "Contains": Match anywhere in the description.
    • "Exact": Only match if the bank statement's description is exactly equal to the provided value.
    • "Regex": Match with regular expressions.
  • Value specifies the value to match against.
  • Category is the category that the statement should be filed under.
  • Description is a short description to distinguish the particular merchant.
  • CaseSensitive specifies whether or not the match should be case sensitive.