Just got an idea for the api import (always getting those ideas after asking about it on a mailing list). I just create a dummy file for the importer, this file can actually even be the config with api key and so on for doing the import
On Saturday, February 3, 2018 at 6:21:14 PM UTC+1, Patrick Ruckstuhl wrote: > > 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 beancount+unsubscr...@googlegroups.com. To post to this group, send email to beancount@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/718b5cc7-7298-4b42-8a48-28cca610f4f3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
