remove STDIN support on execute commands

[nickwesselman]

WHY are these changes introduced?

With the addition of --query-file, we now have 3 ways of specifying the GraphQL query, which is a bit excessive. Reading queries from STDIN is really only useful for echo or cat, and --query and --query-file cover those cases respectively.

Testing of these commands in scripts makes it apparent that if anything, variables should be passable via STDIN. Let's hold off on that, but meanwhile let's reserve STDIN for that possibility.

WHAT is this pull request doing?

• Replaces the exclusive flag constraint with exactlyOne for query input flags to ensure users provide either --query or --query-file
• Removes stdin fallback for query input, requiring explicit query specification
• Updates flag descriptions to remove references to stdin input
• Updates error handling to use BugError when flag validation fails
• Simplifies the prepareExecuteContext function by removing the command name parameter

How to test your changes?

1. Try running shopify app execute without providing either --query or --query-file
2. Verify that you get a clear error message requiring one of these flags
3. Test with valid --query parameter
4. Test with valid --query-file parameter
5. Try using both flags together and verify it fails with appropriate error

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes

[nickwesselman]

• remove STDIN support on execute commands #6734 👈 (View in Graphite)
• Add --query-file flag to app execute and app bulk execute for loading GraphQL queries from files #6733
• Add --variable-file flag to app execute command #6732
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	79.51%	14195/17852
🟡	Branches	73.62%	6967/9464
🟡	Functions	79.63%	3640/4571
🟡	Lines	79.89%	13421/16800

Test suite run success

3567 tests passing in 1416 suites.

Report generated by 🧪jest coverage report action from 6d211c7

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

[ericlee878]

Just curious, what from the testing made you conclude that variables should be passable via STDIN, instead of queries?

[szluzero]

Great DX improvement!

[nickwesselman]

Just curious, what from the testing made you conclude that variables should be passable via STDIN, instead of queries?

Good question. The fact that I was using previous query results to drive mutations primarily. And realizing how damn powerful jq is. I could easily see scripts that do something like shopify app execute --query <query> | jq <transformation and merging> | shopify app execute --query <mutation>