Jakob Schnitzer
Jakob Schnitzer
Either works for me, maybe a slight tendency towards the separate column (make for easier sorting and styling)
I don't really intend for the transaction form to support every intricacy of Beancount's syntax. At some point, I don't think there's much to be gained and writing the transaction...
> here's why I think entering transactions directly in the editor is far less convenient. I hear you - there's definitely aspects where the transaction form excels :) I mostly...
There's already the autocomplete which suggests your most common currency, so I don't think this is needed.
Yes, maybe this could be quickened by more aggressively autocompleting the currency. Using the `selectFirst` prop for the Autocomplete Svelte component could do the trick.
Hey, thanks for the report. An even simpler way to reproduce this is to just press the `r` key to reload the account journal (which is also done on saving...
I don't think there's much we can do here (in the future moving more of the rendering to the frontend might fix this).
Hey, thank you for this PR :) I quite like this kind of visualisation and since it's more compact than the sunburst charts I'm also happy to add another kind...
A PR implementing this would be very welcome :)
This feels like something you should be using tags for, not metadata. Tags are there to group entries into some sets (and I think the prime example in Beancount's documentation...