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

Should --arg= actually delete arg, not set it to empty? #42

Open
1 of 2 tasks
xparq opened this issue Nov 1, 2023 · 0 comments
Open
1 of 2 tasks

Should --arg= actually delete arg, not set it to empty? #42

xparq opened this issue Nov 1, 2023 · 0 comments
Labels
question Further information is requested

Comments

@xparq
Copy link
Owner

xparq commented Nov 1, 2023

The use case is repeating arg with --arg to override any prev. settings.

--arg can kinda still set to empy, albeit it's semantics is a predicate (bool), not "set to empty"!... It's "emptiness" just means [] returns true, but () still returns ""...

But... Even though the override logic should be fixed here (#16!), it's still up to the app, actually, to decide what to do with (arg) == "" or [app] == false, or any other values!

  • Clean up the semantics!,,, It could be equally unexpected to some/in some cases to set --thing= but have [thing] as false!
@xparq xparq added the question Further information is requested label Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant