add support for Beancount v3 #1859
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yagebu
force-pushed
the
beancount-v3
branch
5 times, most recently
from
a5860b0
to
3c7495f
Compare
yagebu
force-pushed
the
beancount-v3
branch
3 times, most recently
from
00a01fd
to
db936d9
Compare
This uses beanquery to replace the functionality in beancount.query, which works with both Beancount v2 and v3 - however there are some differences on columns in beanquery compared to beancount.query. For importers, this sticks to beancount.ingest on v2 and used beangulp for v3. It still expectes importers to conform to the v2 importer protocol for now. Due to changes related to duplicate detection, duplicate detection is not automatically done by Fava here but can still be manually specified as hooks.
yagebu
force-pushed
the
beancount-v3
branch
from
db936d9
to
7132586
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This uses beanquery to replace the functionality in beancount.query,
which works with both Beancount v2 and v3 - however there are some
differences on columns in beanquery compared to beancount.query.
For importers, this sticks to beancount.ingest on v2 and used beangulp
for v3. It still expectes importers to conform to the v2 importer
protocol for now. Due to changes related to duplicate detection,
duplicate detection is not automatically done by Fava here but can still
be manually specified as hooks.