Transaction validation: date range

[Entea]

Implements #85

[coveralls]

Coverage increased (+0.3%) to 68.288% when pulling 8863c2c on Entea:transaction_validation_date_range into 0f0ddf9 on hrj:master.

[hrj]

For parsing the constraint dates, you could use the same date-parser as used in the .ledger parser. So the date format will match the one in the .ledger.

[hrj]

Looks great, thanks!

Apart from the review comments, one more thing remains: we need to add a "suppress error" directive, for posting opening balances.

[Entea]

@hrj how exactly this directive should look like? An entry in config file? Or is it about the #93

[hrj]

While MIN and MAX works in most cases, it is hackish. It would be better to use something like this (pseudo code):

dateFrom.map(_ compare post.date).getOrElse(true)

[hrj]

@Entea Yeah, we can follow it up later in #93

The idea is to let the user specify a reserved tag that forcefully accepts a transaction even if it is out of the date-range.

[coveralls]

Coverage increased (+0.7%) to 68.661% when pulling 8273dff on Entea:transaction_validation_date_range into d570296 on hrj:master.

[Entea]

@hrj Removed the MAX, MIN, thanks for the hint! Squashed the commits into one, should be ready for merging :) Had to downgrade scalatest to 2.2.6 though.

[coveralls]

Coverage increased (+0.7%) to 68.661% when pulling 8273dff on Entea:transaction_validation_date_range into d570296 on hrj:master.

[hrj]

💯 for taking care of everything :)