That's probably good enough. So the unique key for a marker would be (year, string).
The other design option would be for the non-dated directive to produce some sort of a map, and fail if the markers aren't unique. Finally, there's always the option of creating a markerless method (the classification I suggested earlier). On Sat, Mar 31, 2018 at 2:24 AM, 'Patrick Ruckstuhl' via Beancount < beancount@googlegroups.com> wrote: > I think the date might actually have a meaning. E.g. if you split files by > year you might have one marker in one file and another in the other and > based on the date of the transaction it should go to the right one. > > -- > You received this message because you are subscribed to the Google Groups > "Beancount" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beancount+unsubscr...@googlegroups.com. > To post to this group, send email to beancount@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beancount/4d84116e-6b3a-4210-9c6d-9b2514c0c5a0%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To post to this group, send email to beancount@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhP%2BEHN05h0ZttOfspQQQfE-awZ1hh5xjExZmr6KLP%3DVLw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
