(max|min)imum(By)?Def are being replaced by (max|min)imumBound(By)?
but the old functions have the semantics I want and
I don't understand the new ones yet.
This can hide other deprecation warnings in this file,
and presumably the old functions will be removed later,
so this is temporary.
Cf https://github.com/ndmitchell/safe/issues/26
It seems like show (toJSON "a") used to give "\"a\"" instead of
"String \"a\"". I haven't found the root cause, it's possible
that this fix won't work if built with older libs.
As a consequence of fixing #457, two rewrite tests fail, because extra
quotes appear in the output of the commands being tested.
These quotes appear in comments which reflect the command which was
run in order to produce the output. Instead of
; generated-posting: = assets:bank and amt:<0
we now get
; generated-posting: = assets:bank and "amt:<0"
Given that the quotes around `amt:<0` are necessary for the command to
work properly, these quotes should really be there in the expected
output.
Hence this commit modifies the expected output of the tests, by adding
in the quotes. This makes the tests pass once more.
Issue #457 pointed out that commands such as
hledger ui 'amt:>200'
failed. This was becasue the process of dispatching from `hledger ui`
to `hledger-ui` (note addition of `-`) lost the quotes around
`amt:>20` and the `>` character was interpreted as a shell redirection
operator, rather than as part of the argument.
The machinery for quoting or escaping arguements which cointain
characters which require quoting or escaping (thus far whitespace and
quotes) already existed. This solution simply adds shell stdio
redirection characters to this set.
Fixes#457
csb2format deals with the CSB43/AEB43 format, which all banks operating in
Spain must support.
Having these example rules enables easens bootstraping for users with a
Spanish bank account.
