this post was submitted on 28 Jan 2024
32 points (94.4% liked)

Programming

17378 readers
153 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago
MODERATORS
snowe
Ategon
[email protected]
32
In CLI design, how to ask the user for a nested structured input? (lemy.lol)
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/programming
24 comments fedilink hide all child comments
 

Background

I am designing a CLI for a container build tool I am making. It uses Gentoo's Portage behind the scenes

Question

I want to give the user the ability to specify a custom package repository. The repository must have a name, URI and sync type.

custom_repo: {
    uri: 'https://...',
    name: 'custom',
    sync_type: 'git',
}

How do I have the user represent this in the CLI? keep in mind, this is not the main input and is optional.

One way is to make this only provide-able via a config file using JSON or another structured data representation. But I want to see if theres a good way to do it in the CLI

What I am thinking of: command --custom-repo uri='https://...',name=custom,sync_type=git --custom-repo ... [main input]

Is this the best way of doing this?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 9 months ago

perhaps also useful in this case to document the shortcut of

<(echo ‘{…}’)

since not many people know about it, and it makes your tool work with things specified entirely on the command line rather than temp files

alternatively —config-file and —config-json or similar

making and cleaning up temp files when writing scripts is just such a massive PITA