You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am migrating from beancount 2 to beangulp, and I see that there is no standard OFX importer (there is one in the examples but there is not one in the library).
If I implemented it based on the one in the examples and added tests, would such PR be approved (or was there a reason to omit it in the new library)? If it's ok, do you have any preferences for the libraries I should use or what features it should include?
The text was updated successfully, but these errors were encountered:
The reason to move the OFX importer to the examples is to do not have to maintain it as a complete and versatile solution. Actually, there has been some talk about dissing the CSV importer too, but it is has too many users for such a drastic measure. OFX is a very loose specification that every banks seem to interpret in a slightly different way and supporting all variations is not something we are looking forward to do.
IMHO being included in beangulp does not offer any advantage to a framework for OFX importers, thus I encourage you to start a separate project for that.
I am migrating from beancount 2 to beangulp, and I see that there is no standard OFX importer (there is one in the examples but there is not one in the library).
If I implemented it based on the one in the examples and added tests, would such PR be approved (or was there a reason to omit it in the new library)? If it's ok, do you have any preferences for the libraries I should use or what features it should include?
The text was updated successfully, but these errors were encountered: