dev-call build-artifacts fails when schema changes affect type definitions

[cderv]

When making schema changes that affect TypeScript type definitions, dev-call build-artifacts fails type checking before it can regenerate the types - a chicken-and-egg problem.

Example

Adding a new option to logo-light-dark-specifier in definitions.yml:

- id: logo-light-dark-specifier
  anyOf:
    - enum: [false]  # NEW
    - ref: logo-specifier

Then updating code to handle the new option:

if (spec === false) {
  return undefined;
}

Running build-artifacts fails:

TS2367 [ERROR]: This comparison appears to be unintentional because the types 
'string | objectOutputType<...>' and 'boolean' have no overlap.
  if (spec === false) {
      ~~~~~~~~~~~~~~

The types haven't been regenerated yet, so TypeScript doesn't know spec can be false.

Current workaround

Add // @ts-ignore temporarily, run build-artifacts, then remove the comment.

Suggestion

We could add a --no-check flag to dev-call build-artifacts that passes through to Deno, allowing type regeneration to proceed despite temporary type mismatches.

[gordonwoodhull]

We've had this problem for a while.

I don't use our built-in dev commands for this because I don't know when they will fail. Instead I have a script based on the comment

quarto-cli/src/resources/types/schema-types.ts

Lines 3 to 6 in 5e05270

	// If you find yourself trying to rebuild types and `quarto dev-call build-artifacts` won't run because
	// of bad type definitions, run the following:
	// $ cd $QUARTO_ROOT
	// $ ./package/dist/bin/tools/deno run --importmap=./src/import_map.json --allow-all ./package/src/common/create-schema-types.ts ./src/resources

P.S. Thanks for looking at logo: false!