[CLI] Change --no-* commands to --disable-*

[tsriram]

Resolves #4820

[gatsbybot]

Deploy preview for using-drupal ready!

Built with commit 949b3f2

https://deploy-preview-4832--using-drupal.netlify.com

[borekb]

Sorry that I was late to comment but I think --no-xyz is better than --disable-xyz (the --no- prefix seems to be preferred by most CLIs). Originally commented here: #4820 (comment)

A possible way to "fix" the --no-uglify parsing is to configure yargs with boolean-negation: false or maybe define the uglify parameter and let yargs do its negation magic.

[tsriram]

Hmm, I'm quite not sure which is better. Will let @KyleAMathews take a call 😄

Feel free to close this PR if --no-* prefix is the way we want to go.

[KyleAMathews]

Yeah, actually just defining uglify and setting it to default to true sounds like a good solution. Can we only show --no-uglify in the docs?

[tsriram]

Yeah, we can set uglify to true by default, but we'll have to remove boolean-negation option to let users use --no-uglify as a command.

gatsby/packages/gatsby-cli/package.json

Line 51 in 0cf4428

"boolean-negation": false

I couldn't find a way to show only --no-uglify in the docs!

[m-allanson]

Maybe the docs message could be something like:

Uglify JS bundles. Defaults to true. For debugging use --no-uglify to build with non-uglified JS bundles.

[tsriram]

Hmm, that could work. Looking at @KyleAMathews' comment #4820 (comment), I'm not sure if we just want to leave the command as is & close this PR? Happy to make the change if we want to get this in.

[m-allanson]

Hmm. Let's close this for now and revisit if needed. Thanks @tsriram, as always!