Skip to content

Use custom flag to identify regular transactions #2

@maread99

Description

@maread99

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    code improvementEfficiency improvement, efficacy unchanged (refactoring, speed improvements etc)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions