Fix confusing error message when query is empty#6787
Merged
ericlee878 merged 1 commit intomainfrom Jan 22, 2026
Merged
Conversation
Contributor
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success3689 tests passing in 1431 suites. Report generated by 🧪jest coverage report action from cf3caf4 |
Contributor
|
We detected some changes at Caution DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release. |
f6cb114 to
52e54ff
Compare
dmerand
approved these changes
Jan 22, 2026
52e54ff to
4b46286
Compare
4b46286 to
cf3caf4
Compare
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
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.

Resolves: https://github.com/orgs/shop/projects/208/views/34?pane=issue&itemId=3840291657&issue=shop%7Cissues-api-foundations%7C1312
Problem
The code would reach this
BugError, which it should never reach. This was because when a query or query file was blank, it was considered "provided" by oclif (satisfying the exactlyOne constraint) but empty by the code.Solution
Added validation that checks if the query or query file content is blank, and throws a user-friendly error message instead of falling through to the
BugError.Test plan
--queryflag--queryflag with only whitespaceBefore and After
Before:
--queryor empty--query-file:After:
For empty

--query:For empty

--query-file: