The effective_date plugin <https://github.com/redstreet/beancount_reds_plugins/tree/main/beancount_reds_plugins/effective_date#readme> does what you want, I believe. If not, you can find code relating to options_map in that repo.
On Saturday, November 23, 2024 at 11:47:12 AM UTC-8 James Edington Administrator wrote: > I'm trying to make a plugin to enable temporal settlement, where different > legs of a transaction occur at different dates (to cover the major > use-cases of “money is in clearing, you lost time value”, “merchants billed > you very late, you gained time value”, etc.) > > It's going *very* well so far, except that I can't figure out how to > cause my plugin to ingest custom values for options_map; Beancount always > complains that my custom option is an “invalid option”. Does anyone know > how to declare those? > > > https://gist.github.com/98dedad9d856402f7688c47288e53eba/c40c7f4efd0b740012e12134e7bdf17cf95c29f9#file-temporal_settlement-py-L123 > > -- 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 view this discussion visit https://groups.google.com/d/msgid/beancount/dba32380-c347-40d9-9614-d97130f54bc4n%40googlegroups.com.
