>>>>> John Wiegley <[email protected]> writes: > I found this out because I sat down today to add this very feature to > Ledger. My first step was to write a test proving that it didn't work, when > in fact it is doing just what I needed it to do!
Found a slight wrinkle here: It works fine for one transaction, as in the test, but when there are multiple, they collide with each other (because the system doesn't know yet that a UUID will occur multiple times). I think this will mean postponing balance assertion checking until the very end of the parse, so that I can be sure to have resolved all identities. I also want to add the following: - A flag to ignore balance assertions altogether. This can be useful when trying to track something down. - If multiple entries with the same UUID are found, merged their metadata in some way. John -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
