chore: add type generation improvements for ts

[ChiragAgg5k]

What does this PR do?

• Add ability to generate types to specific file
• Fix optional attributes using ? instead of | null
• Fix Models import error
• Improve formatting and add auto-generated comments

Test Plan

Related PRs and Issues

Have you read the Contributing Guidelines on issues?

yes

[Copilot]

Pull Request Overview

Adds improvements to the TypeScript type generation in the Appwrite CLI, including single-file output support, optional property syntax, and import/formatting fixes.

• Introduce --output as a file path for single-file languages and validate directory vs. file output.
• Switch optional model attributes from | null to the ? shorthand and update import statements.
• Enhance templates with auto-generated comments and cleaner enum formatting.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
templates/cli/lib/type-generation/languages/typescript.js.twig	Update type rendering: optional ?, import type Models, add regen instructions.
templates/cli/lib/commands/types.js.twig	Detect file vs. directory output, support single-file destinations, error on mismatch.

Comments suppressed due to low confidence (2)

templates/cli/lib/commands/types.js.twig:69

• [nitpick] The alias rawOutputPath for rawOutputDirectory may be confusing; consider renaming the function parameter to rawOutputPath directly or removing the extra alias for clarity.

  const rawOutputPath = rawOutputDirectory;

templates/cli/lib/commands/types.js.twig:71

• Add unit tests for the new single-file output logic (e.g., when isFileOutput is true and meta.isSingleFile()), to ensure correct path resolution and error handling.

  const isFileOutput = !!outputExt;

[Copilot]

The error message could include the invalid path value to aid debugging, e.g., Invalid output path: ${rawOutputPath}. Directory required for multi-file languages.

Suggested change

	throw new Error("Output path must be a directory for languages that generate multiple files.");
	throw new Error(`Invalid output path: ${rawOutputPath}. Output path must be a directory for languages that generate multiple files.`);

[Meldiron]

This is too complex for me, sorry. Can you show me what this code looks like generated?

[ChiragAgg5k]

the change is just to remove the comma at the end of enum class:

before:

export enum Gender {
  MALE = "male",
  FEMALE = "female",
  NON_BINARY = "non-binary",
}

after:

export enum Gender {
  MALE = "male",
  FEMALE = "female",
  NON_BINARY = "non-binary"
}

[Meldiron]

Let's do basic QA, make sure this work in scenarios like:

• Folder name but with a dot (not file)
• file in nested non-existing folder

[ChiragAgg5k]

• just a dot generates a normal file:

• using nested non existing folder creates it:

• using nested non existing folder + file name creates it as well