fix: update parseArgs tests to match new null-return behavior#132
Merged
julianbenegas merged 1 commit intomainfrom Feb 1, 2026
Merged
fix: update parseArgs tests to match new null-return behavior#132julianbenegas merged 1 commit intomainfrom
julianbenegas merged 1 commit intomainfrom
Conversation
The parseArgs function now returns null and prints help instead of throwing errors for invalid input. This is better UX for a CLI tool since users see helpful usage info instead of stack traces. Updated 6 tests to expect null returns: - Missing -- separator - Missing command after -- - Missing repo - -ref flag without value - -v flag without value - Unknown flag
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
The parseArgs function now returns null and prints help instead of
throwing errors for invalid input. This is better UX for a CLI tool
since users see helpful usage info instead of stack traces.
Updated 6 tests to expect null returns: