Hi, I'm looking at some specific cases for importers and wondering what the best way to tackle this is:
-API based import For some transactions there's a REST api I can use to fetch the transactions. So there is no file to use with the bean-extract framework. I currently created a custom script which works but I would like to unify the different importers if possible. - Using prices in imports For some imports I would like to enhance the transactions with prices based on current/daily price, I'm currently fetching and storing prices in beancount, so prices are available in the beancount file but I'm not sure what the best way to hook this into the importer framework is How do you deal with things like that? Do you ignore bean-extract tools and just create independent scripts? Regards, Patrick -- 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/29e70aca-b985-5291-38fc-93c2d80956d4%40ch.tario.org. For more options, visit https://groups.google.com/d/optout.
