Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize how command options work #217

Open
meza opened this issue Jan 26, 2023 · 0 comments
Open

Standardize how command options work #217

meza opened this issue Jan 26, 2023 · 0 comments
Labels
enhancement New feature or request planned This feature is planned to be developed

Comments

@meza
Copy link
Owner

meza commented Jan 26, 2023

Currently we use --quiet, --force and --dry-run for all sorts of things and they're most definitely not consistent.

I'm imaging a re-work where we have the following:

-i, --non-interactive - to suppress CommanderJS outputs
-q, --quiet - to suppress ALL outputs and communicate solely through exit codes
-n, --dry-run - to prevent making changes to the configuration or the filesystem. Would also print out information about what would have happened.
-f, --force - do things without asking questions. It would be the equivalent of the --non-interactive mode in most cases. Where it would be different is during destructive operations. Would not ask to remove files for example.

This is still a work in progress theory, please feel free to contribute.

@meza meza added enhancement New feature or request planned This feature is planned to be developed labels Jan 26, 2023
@meza meza changed the title Standardize how command options work [RFC] Standardize how command options work Jan 26, 2023
@meza meza pinned this issue Jan 26, 2023
@meza meza moved this to RFC in Minecraft Mod Manager Feb 3, 2023
@meza meza modified the milestone: 1.3.0 Dec 21, 2023
@meza meza moved this from RFC to Todo in Minecraft Mod Manager Aug 30, 2024
@meza meza changed the title [RFC] Standardize how command options work Standardize how command options work Aug 30, 2024
@meza meza unpinned this issue Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request planned This feature is planned to be developed
Projects
Status: Todo
Development

No branches or pull requests

1 participant