I'd recommend exactly that as the first step---spitting out text files of
the write format, and using that with your workflow for a while. You'll
either find that sufficient, or truly understand the specific problems you
want to solve, and be able to pick the right framework with that knowledge.
Beancount has a built in generic CSV importer, I'd suggest trying that
first. That'll get you bean-{identify, extract, file} for free. If you need
the heavy lifting of investments, find yourself solving similar problems
across multiple importers, or find your workflow could be smoother, my
importer framework can help.
On Sunday, July 16, 2023 at 8:34:59 PM UTC-7 [email protected] wrote:
> I have a few CSV files with basic transactions (basically sent and
> received assets & amounts, plus commission cost). These are all I need to
> process. It would be pretty easy for me to just translate them line by
> line into Beancount format inputs, but I like to do things "the right
> way". Problem is, I can't figure out what "the right way" is :)
>
> I spent a long time exploring the importer framework before realizing that
> it was the old one, tossed out for v3. I have now read the design doc for
> the v3 importer system, the readme, skimmed the code and some examples, and
> then read some threads on this list which also led me to RedS's CSV
> framework, which I also looked into.
>
> Am I trying too hard? Should I just ignore the frameworks and spit out
> text files of the right format? If I should use a framework...which would
> folks recommend?
>
> thanks,
> eric
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/c091350e-c0f5-45af-9a64-35bd17ae76f7n%40googlegroups.com.
