conservancy_beancount/tests/books/books/2019.beancount

option "title" "Books from 2019"
include "../definitions.beancount"
include "../2019.beancount"
books.Loader: New loading strategy. The old loading strategy didn't load options, which yielded some spurious errors. It also created awkward duplication of plugin information in the code as well as the books. Implement a new loading strategy that works by reading one of the "main files" under the books/ subdirectory and includes entries for additional FYs beyond that. This is still not ideal in a lot of ways. In particular, Beancount can't cache any results, causing any load to be slower than it theoretically could be. I expect more commits to follow. But some of them might require restructuring the books, and that should happen separately. 2020-05-05 14:31:08 -04:00			`option "title" "Books from 2019"`
books.Loader: New loading strategy based on load_file. RT#11034. Building a string and loading it means Beancount can never cache any load. It only caches top-level file loads because options in the top-level file can change the semantics of included entries. Instead use load_file as much as possible, and filter entries as needed. 2020-05-16 10:27:06 -04:00			`include "../definitions.beancount"`
books.Loader: New loading strategy. The old loading strategy didn't load options, which yielded some spurious errors. It also created awkward duplication of plugin information in the code as well as the books. Implement a new loading strategy that works by reading one of the "main files" under the books/ subdirectory and includes entries for additional FYs beyond that. This is still not ideal in a lot of ways. In particular, Beancount can't cache any results, causing any load to be slower than it theoretically could be. I expect more commits to follow. But some of them might require restructuring the books, and that should happen separately. 2020-05-05 14:31:08 -04:00			`include "../2019.beancount"`