`check` command should not stop after the first error about hledger HOT 4 OPEN

Not detracting from your point, but remember strict account checking is optional and simply avoiding it is another option when the chart of accounts hasn't yet stabilised.

from hledger.

Yes, I know, but strictness checking is also the only way to know which accounts have not been declared and are being used. One can always get the used accounts' listing from a non-strict hledger accounts, but it has its downsides.

Thank you for the suggestion, though.

from hledger.

I'd be happy to test a PR exploring this. Some checks are relatively easy to continue from on failure; others are not.

But I don't find it causing pain in practice, do you ? I don't have a slow edit-check-fix cycle.

from hledger.

I'd be happy to test a PR exploring this. Some checks are relatively easy to continue from on failure; others are not.

Maybe one day. Right now my Haskell skills are subpar and I have no familiarity with hledger's code base (sadly). I'll try and change that in the future.

But I don't find it causing pain in practice, do you ? I don't have a slow edit-check-fix cycle.

In a carefully maintained chart of accounts this isn't problematic (especially if one has some kind of auto-complete for account names), but scenarios vary.
I recently started tracking my finances with hledger and there was a lot of checking and fixing to do in the beginning (because my chart of accounts wasn't fully developed).

Still, on a more general note, I think having the check command try and report as many errors as it can is a positive change, while passing the --strict flag should still quit after the first error is found.

from hledger.