Remove defaultValueDescription: "n/a" from options

[jablko]

Are there different meanings to defaultValueDescription: "n/a" and omitting defaultValueDescription?

/cc @orta

[typescript-bot]

This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise.

[jablko]

Also, what do you think about refining the CommandLineOption type like so, to check .type <-> .defaultValueDescription agreement?

[orta]

Yeah, this seems reasonable to me - it doesn't look like a breaking change, but would be nice to have at least one other person take a look over it.

Switching from n/a is good simply because n/a is a tad ambiguous anyway.

[jablko]

Thanks! I've now added a third commit to drop the optional modifier from CommandLineOptionOf{Number,Boolean}Type.defaultValueDescription. This checks for a defaultValueDescription of e.g. exactOptionalPropertyTypes, noFallthroughCasesInSwitch, noUncheckedIndexedAccess, noImplicitOverride, etc. (which I added in the same commit).

That adds default: false to the tsc --all output, like other options, e.g.

I added the commit to this PR because it builds on it, but I'm happy to move it to a separate PR if you prefer.

Here's the list of options I added defaultValueDescription: "false" to, to satisfy the refined CommandLineOptionOfBooleanType:

• synchronousWatchDirectory
• help
• watch
• preserveWatchOutput
• explainFiles
• assumeChangesOnlyAffectDirectDependencies
• all
• version
• init
• build
• showConfig
• listFilesOnly
• useUnknownInCatchVariables
• exactOptionalPropertyTypes
• noFallthroughCasesInSwitch
• noUncheckedIndexedAccess
• noImplicitOverride
• preserveSymlinks
• experimentalDecorators
• emitDecoratorMetadata
• stripInternal
• disableSourceOfProjectReferenceRedirect
• disableSolutionSearching
• disableReferencedProjectLoad
• preserveConstEnums
• preserveValueImports
• verbose
• dry
• force
• clean
• enableAutoDiscovery
• enable
• disableFilenameBasedTypeAcquisition