You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently regular transactions are flagged '!' and tagged 'reg_txn'. The tag allows them to be identified. It might be preferable for a custom flag to do this job although the lexer for beancount v2 is hardcoded to only recognize flags defined in beancount.core.flags. If beancount v3 provides for custom flags consider using flags to identify expected transactions, for example, 'XR' for a regular expected transaction.
(EDIT Jun 24) HOWEVER, would need to maintain v2 compatibility until v3 becomes established. i.e. this is perhaps something to consider only when it'd be reasonable to drop support for v2.
The text was updated successfully, but these errors were encountered:
Currently regular transactions are flagged '!' and tagged 'reg_txn'. The tag allows them to be identified. It might be preferable for a custom flag to do this job although the lexer for beancount v2 is hardcoded to only recognize flags defined in
beancount.core.flags
. If beancount v3 provides for custom flags consider using flags to identify expected transactions, for example, 'XR' for a regular expected transaction.(EDIT Jun 24) HOWEVER, would need to maintain v2 compatibility until v3 becomes established. i.e. this is perhaps something to consider only when it'd be reasonable to drop support for v2.
The text was updated successfully, but these errors were encountered: