feat: balance option --full-path#2661
Conversation
|
I'm afraid I don't really understand this or #2429. And I'm a bit worried about flag proliferation. Draft docs / examples / use case will be helpful. |
|
I hoped that #2429 would explain well enough what I need the option for. I'll try to add a simplified example. Summarised I need the option for using VLOOKUP in LibreOffice for accessing numbers provided by Hledger in a FODS table. I agree with your worries about flag proliferation. I do not have very good ideas for that problem other than making the flags more principled. We could also make full-path the default for FODS and CSV export, since these are intended for machine-processing. However, I tried hard to unify export to HTML, CSV, FODS before. |
|
That helped, thanks. This new general report flag only affects tree mode balance reports' FODS output, I see. |
|
More precisely: currently it's a new balance command flag, affecting only the tree-mode FODS output, but it's stored in the general ReportOpts. |
|
In its present form it feels a bit inconsistent. One might expect it to affect all reports that can show a tree of account names. Would this be another way to get the same info: make list mode balance reports include all the normally-elided parent accounts, when --no-elide is used ? |
|
As I have written in #2429, I also tried adding parent accounts to List Mode, but adding full paths to Tree Mode turned out much simpler. |
|
You can see here my first attempt to add parent accounts to the List View: |
|
I see. From a UX perspective, it sounds nice if we could reuse --no-elide, since it's already there, has the right sort of meaning, and currently has no effect on list mode reports. |
|
I can have a look at it also if helpful. |
|
On Wed, 15 Jul 2026, Simon Michael wrote:
[10144?s=20&v=4] simonmichael left a comment (simonmichael/hledger#2661)
I see. From a UX perspective, it sounds nice if we could reuse
--no-elide, since it's already there, has the right sort of meaning, and
currently has no effect on list mode reports.
That is, --no-elide was left unimplemented for list mode for lack of time
or so and it would be the preferred option for what I intended with the
--include-parent option?
I remember that List Mode with --include-parent did not quite do the right
thing for me, but Tree Mode with --full-path did. I have to look again,
what the difference actually was.
|
cc5f328 to
424f3f6
Compare
|
Yes I think reusing --no-elide would be preferred, if it would give the required info and it's not too much of a pain to implement.
It was added for tree mode. At the time I saw no particular effect it should have on list mode. But now we may have found one, which means we could convert this niche mode-specific flag into a slightly more general one.
|
|
On Wed, 15 Jul 2026, Simon Michael wrote:
It was added for tree mode. At the time I saw no particular effect it
should have on list mode. But now we may have found one, which means we
could convert this niche mode-specific flag into a slightly more general
one.
Then I will try to implement --no-elide for List Mode.
|
|
On Wed, 15 Jul 2026, Simon Michael wrote:
[10144?s=20&v=4] simonmichael left a comment (simonmichael/hledger#2661)
Yes I think reusing --no-elide would be preferred, if it would give the
required info and it's not too much of a pain to implement.
I see in my records that I even tried to get the desired account selection
using the --no-elide option in the past.
|
2 participants
This is a draft for #2429. If you accept it, it still needs some documentation. It serves my needs for a year now, however I am unhappy that we may add a lot of these options in the future that alter an aspect or another of selecting accounts and adapting their formatting. Hledger started with a set of configurations that were useful but now it turns out that sometimes you need to alter individual items in the configurations.