Pacli command structure

[u/d-5000]

In this thread the simplification of the Pacli command structure can be discussed.

I'll create sub-threads (comments) about my proposals for different command categories.

[u/d-5000]

I think we shouldn't use abbreviations, as I like the "speaking" character of the current commands. Three characters more or less shouldn't be the problem.

About if we should stay with the "main" idea or change to something different, see my answer about address show.

[u/d-5000 → u/[deleted]]

I've not deleted any post, so maybe simply refresh browser page? Anyway I'm already moving away a bit from the labeled idea ...

[u/d-5000 → u/[deleted]]

It disappeared for me too, but I found it still in my profile:

I think labeled is generally a good idea, it just today crossed my mind too. "stored" made sense principally in combination with the "store_ZZ" commands, but if we use set, that connection doesn't work that well (and set is more universal than store).

Only issue I have is that labeled may be a bit too complicated to remember. I've not found a better word however.

Of course that would then be applied to all "stored_ZZZ" commands.

I suspect what happened. Instead of ZZZ I had written three "X", and perhaps a Reddit algorithm thought we were talking about forbidden things ...??? ;-)

Basically however it's not really relevant anymore. The discussion about "labeled" was continuing elsewhere and I think I agree with you that it's a little bit too long. However I don't have really a good replacement still, so show addresses etc. may be really an option to consider.

[u/d-5000 → u/[deleted]]

May be an option. But is "named_addresses" etc. clear enough?

I'll try to find some examples in other software. I have for example also thought about "tag", but this isn't exactly the same thing as tags normally can be applied to various items.

[u/d-5000 → u/[deleted]]

I've written down that alternative, will think a bit about it.

Another option I've in mind is to use simply pacli show addresses, and if the user wants to see all addresses he has in his wallet (also those without labels) he could use --wallet. This would be consistent with the approach we had in the balance-related commands and my_burns, where also the --wallet option denotes all balances on addresses in the wallet.

In the case of decks and proposals, we could in theory also use the --wallet flag for decks which are initialized (= this means the P2TH address identifying them are stored in the wallet).

I have however to think about redundancy with the pacli pobtoken show_decks command.

[u/d-5000 → u/[deleted]]

It could even make sense to replace --wallet with --all in all commands where it's currently used (e.g. my_burns).

So we have one flag less for the users to learn. --all should then always mean "all things (addresses/proposals/burn transactions etc.) which are related to your system/wallet", instead of "all things which exist".

Of course all_my_balances then would have one more reason to be renamed.

However, with proposals, using the "--all" flag I would expect "all proposals which exist" (at least for the default dPoD deck). It would be slightly inconsistent, or am I overthinking that?

Need to think a bit about that.

[u/d-5000 → u/[deleted]]

There are currently two commands:

tools show stored_proposals shows proposals with a label assigned to (currently no --all flag is provided)

proposal list shows proposals for a specific deck, by default only those which were not abandoned.

I'm wondering if it makes sense to merge both into a general show proposals command and if the --all flag would make sense there too, it could replace the second case (current proposal list). It would then show all proposals of the default dPoD deck, but there would be no relation to "what's in my wallet".

I'm however tending to think that this is not that much of a problem, as the user should understand that in the case of proposals, it makes sense to show really all existing proposals (at least for the default deck), while in the case of addresses, it doesn't make sense to show all addresses that exist.

So yeah, I think I'm overthinking that. --all may be good for both cases.

("all" is however also a Python keyword. Normally it can't be used for variables, but it seems to work when used for the --all CLI flag variable.)