On Monday, May 27, 2024 at 7:32:52 PM UTC-7 [email protected] wrote:
On Wednesday, May 22, 2024 at 9:59:14 AM UTC+7 Red S wrote: Mini rant: I’d love for anyone who writes an importer to come to the same realization Felipe did, and *write it using the beangulp API*. I have several written several importers. I've never looked at moving them to beangulp. Because when I look at beangulp's github repository there are no releases, no commits in 8 months, and the "Status" documentation says "As of February 2021, the project has just been forked out of Beancount. Expect some changes to be made here." I assume, perhaps incorrectly(?), that if beangulp isn't in a state to be released yet then it isn't in a state for me to migrate my importers to it. I’ve done the same thing for exactly the same reasons, and thus, beancount_reds_importers <https://github.com/redstreet/beancount_reds_importers> is written against bean-{identify, extract, file} in Beancount v2 instead of beangulp. Good catch, thank you, I should’ve been more explicit and instead recommended that people write importers against released code, which in this case is Beancount v2’s importers. -- 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/8707764a-7279-4f9b-96c4-86063882b26an%40googlegroups.com.
