Add silence flag to the theme dev commands

[EvilGenius13]

WHY are these changes introduced?

Closes: #4714
I saw a slack post talking about request logs (Ex: • 12:57:27 Request » GET 200 /collections/all 51) are too noisy and they wish they could be disabled.
Fixes #0000

WHAT is this pull request doing?

Add a --silence flag to the theme dev command to disable request logs

Before:

After:

How to test your changes?

Pull down the branch
Build the branch
Run theme dev --silence and click around in your theme links like collections, products, etc.
You shouldn't see any request logs in the terminal.

Post-release steps

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
• Existing analytics will cater for this addition
• PR includes analytics changes to measure impact

Checklist

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

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	75.42%	8743/11592
🟡	Branches	70.71%	4266/6033
🟡	Functions	75.1%	2289/3048
🟡	Lines	75.99% (+0.01% 🔼)	8266/10878

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / app-event-watcher.ts	93.83% (-1.23% 🔻)	86.49% (-2.7% 🔻)	90.48%	98.61%

Test suite run success

1968 tests passing in 892 suites.

Report generated by 🧪jest coverage report action from f338316

[jamesmengo]

To consider: granularity for sync logs ( file upload / download ). Do we need more granularity for how verbose the logs are?

[frandiox]

To consider: granularity for sync logs ( file upload / download ). Do we need more granularity for how verbose the logs are?

Perhaps we should go with a flag that we can extend later instead of (complete) --silence?
For example: --logs=none (defaults to --logs=all. We could later add --logs=request, --logs=request,sync, etc.

There's also --verbose from the CLI itself, we should ensure they don't contradict each other.

Thoughts?

[jamesmengo]

@frandiox 100% on the same page that adding something like --server-logs=<OPTION> gives us more flexibility. One other important consideration that you mentioned is potential conflicts with current / future flags related to output.

My 2 🪙 :

• Flag name: Something like --server-logs is my suggestion, since this makes it clear which logs this pertains to and is less likely to have collisions in the future.
• I love your idea of being able to compose the configuration of logs by providing multiple values. I think this is much more flexible and puts the power in the hands of the users.

[github-actions]

This PR seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action.
→ If there's no activity within a week, then a bot will automatically close this.
Thanks for helping to improve Shopify's dev tooling and experience.