Fix boolean CLI flags swallowing commands and search terms - #49
Merged
ralyodio merged 1 commit intoSep 9, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Title: Fix boolean CLI flags swallowing commands and search terms
agenticjobs search --remote rust --agents developercurrently loses both search words, andagenticjobs --json search rustparsesrustas the command. The parser treats every option as potentially taking a string value.Recognize the CLI's boolean options so they leave subsequent positional arguments intact. Preserve explicit boolean values (
--remote false,--remote=false), string-valued options, repeated application answers, and--.Validation:
api.test.tsandsw.test.ts.no app, and the service-worker asset hash differs. Neither suite is modified by this PR.Prepared with Codex assistance for Anubhab. This is a contribution toward the bug-fix reward advertised at https://ugig.net/gigs/8b2a21db-ce15-433f-a73d-68f2e3349e87 . Please confirm whether this PR qualifies for the listed $0.25 reward and the supported payout route. No reward is being represented as approved or paid.
Formal uGig application:
43ba865e-5a85-434a-b709-ddce36d95bb2(pending at the listed $0.25 rate).