Replies: 2 comments 2 replies
-
Yes. Eventually, we may support everything in the beancount syntax. But I add things as they are needed for a use-case, and I wait for the need to actually arise first. Obviously, a rewrite of Personally, my priority is to first support tags for transactions, then the price directive. After that, my priority will (probably) be to improve the error handling to make clearer what is the problem in case of incorrect syntax. I have personally no use-case for open, close and options. That doesn't mean I won't support them. I will probably implement them sooner or later (they should be very easy to implement anyway) it is just not my priority yet. If you want them to be supported quickly you can contribute them ;-) I convert this into a discussion, as I feel it is not actionable (it kind of say "support the rest of the beancount syntax" 😄). Feel free to create more specific issues (like "support the |
Beta Was this translation helpful? Give feedback.
-
Fantastic! So glad to see that there is a solid outlook for this library! |
Beta Was this translation helpful? Give feedback.
-
Currently the only associated Directive type is a transaction.
At minimum, there should be three additional directive types:
1.Account open & close.
2. Options. (Metadata, usually titles, precision display options, etc.)
I'm starting work on what will become
beancount-rs
and I need to verify that accounts are open.Beta Was this translation helpful? Give feedback.
All reactions