Heya,

On Fri, May 04, 2018 at 02:24:04AM -0700, Justus Pendleton wrote:
> Isn't the link_statements plugin just a regular beancount plugin that
> can be used even if you don't use fava? What would be the difference
> between that plugin and a beancount native way? I'm not quite
> following what you want here; could you elaborate?

sure. So, I see the following issues with the link_statements plugin:

- it is not distributed with beancount, so while the documents option is
  built-in (hinting at the fact that that's the official way of linking
  documents to txns), link_statements seems to be a sub-par / not
  supported

  -> this would be easy to solve if Martin is OK with distributing it as
     part of Beancount, but I think a more general discussion about what
     are the requirements for linking documents to different elements of
     the Beancount data model, which is what I'm trying (probably badly,
     sorry about that) to start here

- it is not alternative to document entries. It requires you to have
  free-floating document entries in your global ledger and then
  heuristically associate them to transactions/postings

  -> this feels awkward. A receipt for the grocery store does not belong
     to the daily flow of transactions happening that day. It really
     belong to a transactions. This smell as if we need a more
     expressive way of informing Beancount of which metadata keys point
     to documents, or something such

- it is not generic (not all documents are "statements")

  -> this is a minor point, which looks like will be fixed soon

Hope this clarifies,
Cheers
-- 
Stefano Zacchiroli . [email protected] . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/20180505080719.GG1361%40upsilon.cc.
For more options, visit https://groups.google.com/d/optout.

Reply via email to