Optionally make commodity directive mandatory?

[Lover O'Bean]

I am new to beancount, but would like the option of requiring that each commodity / currency be created with a commodity directive before being used, in the same way that accounts require an open directive before being used.

For example, if I declare AIRMILES.WN (IATA code) today but two years from now enter a transaction which accrues AIRMILES.SW (vernacular), I would like to get an error, just like if I referred to a nonexistent account.

Is this a good idea, or am I off-base?

[Martin Michlmayr]

There's a plugin for this: validate_commodity_directives

A plugin that verifies that all seen commodities have a Commodity directive.

* Lover O'Bean <lover...@gmail.com> [2023-12-28 17:16]:

> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CABV0qx7m7iR8vYK%2BsgXjGx7UvV0uEsh1WaGE3hpL8eGc8Qiiqw%40mail.gmail.com.

--
Martin Michlmayr
https://www.cyrius.com/

[Lover O'Bean]

Yes; while it doesn't address timing, it should be good enough for now:

https://beancount.github.io/docs/api_reference/beancount.plugins.html#beancount.plugins.check_commodity.validate_commodity_directives

(Also, while I was "in the neighborhood", I noticed another plugin that addresses another concern that I had.)

Thanks Martin!

[Martin Blais]

You're welcome!

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/aaf37c31-dbeb-433a-9257-ca1de809dedfn%40googlegroups.com.