Hi there,

First time making a post here, hopefully it's okay to share open source 
tools I built here. 

I was working on my web base beancount SaaS product and realized that 
adding new entries without formatting over time will soon end up with a 
mess. I really like Python's black formatter and how it works. With the 
needs in mind, I built two projects:

   - 
   
   beancount-parser <https://github.com/LaunchPlatform/beancount-parser> - 
   Standalone Lark based Beancount syntax parser
   - 
   
   beancount-black <https://github.com/LaunchPlatform/beancount-black> - 
   Opinionated beancount code formatter based on beancount-parser
   
Both were open sourced under MIT license (there's no dependency to 
Beancount lib). The reason I don't use Beancount lib is that I want to 
handle things like comments and emac org syntax. It would be much easier 
and cleaner to build a Lark <https://github.com/lark-parser/lark> based 
parser and work on top of that. Since the product I build is SaaS and 
there's zero dependency to the Beancount core, there was actually no 
requirement for open sourcing them. But I really like the plantext 
accounting community and would like to give back as much as I can, so I 
open sourced them here.

You can try the formatter online here if you don't want to install them:

https://beanhub.io/tools/beancount-formatter

Some of the corner case syntax may not be supported, and since the tool is 
pretty new, you may also encounter bugs, please feel free report them or 
provide any feedbacks. There are more features to be added to the formatter 
in the near future, such as

   - 
   
   Account renaming
   - 
   
   Currency renaming
   
Anyway, hope these tools I build could be useful to some of you 😄🙌

-- 
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/baff9409-74cd-44ed-b44f-f243d5781b21n%40googlegroups.com.

Reply via email to