I believe this approach makes sense in limabean because the user interface
is a full-blown programming language, Clojure, and you can do whatever you
need with the list of fully resolved directives that are exposed there
after loading the beanfile.
Makes sense.
Plugins would justify their existence by a need to modify the transactions
earlier, before the booking algorithm has run. Are there compelling use
cases for this?
Some examples: anything that opens
<https://github.com/redstreet/beancount_reds_plugins/tree/main/beancount_reds_plugins/opengroup#readme>,
closes
<https://github.com/redstreet/beancount_reds_plugins/tree/main/beancount_reds_plugins/autoclose_tree#readme>,
or renames
<https://github.com/redstreet/beancount_reds_plugins/tree/main/beancount_reds_plugins/rename_accounts#readme>
accounts. YMMV, of course.
--
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/beancount/699b4206-605b-4baf-8df6-3fd0ecf8653cn%40googlegroups.com.
